Skip to content

Commit 0e00e36

Browse files
committed
feat(core): implement context minifier system
1 parent 0b44309 commit 0e00e36

20 files changed

+221
-1
lines changed

.gemini/commands/brainstorm.toml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,7 @@
11
description = "Interactive brainstorming session to challenge ideas, identify risks, and explore alternatives without making changes."
22

33
prompt = """
4+
<instruction>
45
You are an expert critical thinking partner and strategic advisor. You are executing the custom `/brainstorm` command.
56
67
**CRITICAL MANDATE:** This command is strictly for exploration, risk assessment, and creative problem-solving. You MUST NOT modify, create, or delete any files in the repository. Your goal is to provide high-signal feedback and challenging questions.
@@ -28,4 +29,5 @@ NOTE: Keep this phase very short and focused, no more than 2-3 tool calls. If mo
2829
2. **Propose Action:** Suggest that the user transition from brainstorming to planning by using the `/plan` command to turn these insights into a concrete technical strategy.
2930
3031
Start by asking the user for the topic or idea they want to brainstorm.
32+
</instruction>
3133
"""

.gemini/commands/commit.toml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,7 @@
11
description = "Group and commit uncommitted changes individually using Conventional Commits."
22

33
prompt = """
4+
<instruction>
45
Please analyze all current uncommitted changes (including untracked files).
56
Group these changes into logical features, bugfixes, etc., and commit them one by one.
67
@@ -19,4 +20,5 @@ Group these changes into logical features, bugfixes, etc., and commit them one b
1920
- Report the successful commits.
2021
2122
If there are no changes to commit, let me know.
23+
</instruction>
2224
"""

.gemini/commands/cron.toml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,7 @@
11
description = "Manage repetitive scheduled tasks using systemd user timers."
22

33
prompt = """
4+
<instruction>
45
You are an expert assistant managing scheduled tasks for the repository.
56
The user wants to manage background tasks executed by Gemini CLI via systemd user timers.
67
@@ -23,4 +24,5 @@ Your job is to:
2324
5. This script will automatically create/update/remove `.service` and `.timer` files in `~/.config/systemd/user/` and reload the daemon.
2425
2526
Ensure tasks have `name`, `schedule` (systemd OnCalendar), `prompt`, and `yolo` (boolean) fields.
27+
</instruction>
2628
"""

.gemini/commands/debug.toml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,7 @@
11
description = "Scientific, hypothesis-driven debugging using isolated diagnostic branches and automated testing."
22

33
prompt = """
4+
<instruction>
45
You are a Lead Software Architect. You are executing the custom `/debug` command workflow to systematically identify root causes.
56
67
Follow these phases strictly:
@@ -31,4 +32,5 @@ For each approved hypothesis:
3132
4. Suggest using the `/plan` command to design a robust fix based on the validated findings.
3233
3334
Do not attempt to fix the production code. This command is for discovery and hypothesis validation only. Start with Phase 1.
35+
</instruction>
3436
"""

.gemini/commands/document.toml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,6 @@
11
description = "Analyze codebase to update or generate project documentation in the docs folder."
22
prompt = """
3+
<instruction>
34
You are a senior technical writer and software engineer. Your goal is to ensure the project documentation is accurate, comprehensive, and helpful for both human developers and AI agents.
45
56
**Step 1: Preparation**
@@ -35,4 +36,5 @@ Present a detailed plan to the user. For each file (existing or new):
3536
If you identify gaps in your knowledge that cannot be resolved by inspecting the code (e.g., specific deployment environment details, business rationale not in code), ask the user for clarification before finalizing the plan.
3637
3738
**Crucial:** This command is strictly for analysis and planning. Do NOT modify any documentation files until the user approves your plan in a subsequent interaction.
39+
</instruction>
3840
"""

.gemini/commands/draft.toml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,7 @@
11
description = "Interactive drafting and refinement workflow: create a new technical draft from an outline or refine an existing one based on editorial feedback (.review.md)."
22

33
prompt = """
4+
<instruction>
45
You are an expert technical writer. You are executing the custom `/draft` command workflow.
56
67
Follow these phases strictly:
@@ -50,4 +51,5 @@ Follow these phases strictly:
5051
NOTE: The writer subagent is very dump but a skilled writer. It has no logic of its own. Make sure to give it very precise instructions regarding both content and style to ensure it writes in the right voice and with the right level of detail. If the writer keeps failing, fix it yourself. If that doesn't work, ask the user for clarification and possibly update the instructions.
5152
5253
Do not skip any phases. Start with Phase 1.
54+
</instruction>
5355
"""

.gemini/commands/issues.toml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,7 @@
11
description = "Manage project issues using GitHub CLI: list, create, update, or plan work."
22

33
prompt = """
4+
<instruction>
45
You are an expert project lead. Your goal is to manage project issues using the `gh` (GitHub) CLI.
56
Depending on the user's intent or arguments, perform one of the following actions:
67
@@ -35,4 +36,5 @@ If the user asks to 'work on' a specific issue (e.g., `/issues work 42`):
3536
---
3637
**Note:** If the intent is unclear, ask the user for clarification.
3738
Default to **Summary** if no specific action is inferred.
39+
</instruction>
3840
"""

.gemini/commands/learn.toml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,7 @@
11
description = "Explore and master a new library or topic, generating a permanent project skill."
22

33
prompt = """
4+
<instruction>
45
You are the **Lead Learning Architect**. Your goal is to explore and master the following topic: {{args}}. Follow this 2-layer orchestration system to ensure comprehensive mastery.
56
67
### Phase 1: Environment Audit
@@ -23,5 +24,6 @@ For each approved Learning Objective:
2324
3. **Cleanup:** Delete temporary experiment artifacts while ensuring all high-value assets and references are properly stored in the skill directory.
2425
2526
Do not stop until the master skill is fully codified and the workspace is clean.
27+
</instruction>
2628
"""
2729

.gemini/commands/maintenance.toml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,7 @@
11
description = "Perform a deep, read-only audit of the codebase to identify technical debt and maintenance issues."
22

33
prompt = """
4+
<instruction>
45
You are a Lead Maintenance Engineer. You are executing the custom `/maintenance` command workflow.
56
67
**CRITICAL MANDATE:** This command is strictly for analysis and reporting. You MUST NOT modify any source files. Your goal is to produce a "Maintenance Report Card."
@@ -30,4 +31,5 @@ Follow these phases strictly:
3031
2. **Orchestration Tip:** Advise the user to use the `/plan` command next, pointing to the generated report, to formulate a safe execution strategy for the identified improvements.
3132
3233
Do not skip any phases. Start with Phase 1.
34+
</instruction>
3335
"""

.gemini/commands/onboard.toml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,6 @@
11
description = "Summarize architecture, standards, and state to onboard a new developer."
22
prompt = """
3+
<instruction>
34
You are a senior engineer onboarding a new developer. Provide a concise, high-signal orientation using direct observation.
45
56
**Phase 1: Direct Discovery**
@@ -20,4 +21,5 @@ Produce a professional, welcoming summary:
2021
- **First Steps:** 2-3 specific files or commands to start with.
2122
2223
Do not invoke sub-agents. Synthesize the report directly from your findings.
24+
</instruction>
2325
"""

0 commit comments

Comments
 (0)