MediaMetz/gemini-cli
1
0
Fork 0
mirror of https://github.com/google-gemini/gemini-cli.git synced 2026-03-10 22:21:22 -07:00
Code Issues Packages Projects Releases Wiki Activity

Teach reflect sub-agent about skills.

Browse Source
This commit is contained in:
Christian Gunderman
2026-03-10 13:53:59 -07:00
parent b3f8c90972
commit c31205cad0
2 changed files with 19 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
packages/core/src/prompts/snippets.ts
View File

@@ -340,6 +340,8 @@ export function renderPrimaryWorkflows(
## Development Lifecycle ## Development Lifecycle
Operate using a **Research -> Strategy -> Execution** lifecycle. For the Execution phase, resolve each sub-task through an iterative **Plan -> Act -> Validate -> Reflect** cycle. Operate using a **Research -> Strategy -> Execution** lifecycle. For the Execution phase, resolve each sub-task through an iterative **Plan -> Act -> Validate -> Reflect** cycle.
${renderReflectionWorkflow(options.enableReflection)}
${workflowStepResearch(options)} ${workflowStepResearch(options)}
${workflowStepStrategy(options)} ${workflowStepStrategy(options)}
3. **Execution:** For each sub-task: 3. **Execution:** For each sub-task:
@@ -349,14 +351,13 @@ ${workflowStepStrategy(options)}
**Validation is the only path to finality.** Never assume success or settle for unverified changes. Rigorous, exhaustive verification is mandatory; it prevents the compounding cost of diagnosing failures later. A task is only complete when the behavioral correctness of the change has been verified and its structural integrity is confirmed within the full project context. Prioritize comprehensive validation above all else, utilizing redirection and focused analysis to manage high-output tasks without sacrificing depth. Never sacrifice validation rigor for the sake of brevity or to minimize tool-call overhead; partial or isolated checks are insufficient when more comprehensive validation is possible. **Validation is the only path to finality.** Never assume success or settle for unverified changes. Rigorous, exhaustive verification is mandatory; it prevents the compounding cost of diagnosing failures later. A task is only complete when the behavioral correctness of the change has been verified and its structural integrity is confirmed within the full project context. Prioritize comprehensive validation above all else, utilizing redirection and focused analysis to manage high-output tasks without sacrificing depth. Never sacrifice validation rigor for the sake of brevity or to minimize tool-call overhead; partial or isolated checks are insufficient when more comprehensive validation is possible.
**Reflect** -- Reflect on your learnings. **Reflect** -- **CRITICAL** always perform the 'Reflecting on your learnings' workflow after you are done working to preserve your knowledge for subsequent sessions.
## New Applications ## New Applications
**Goal:** Autonomously implement and deliver a visually appealing, substantially complete, and functional prototype with rich aesthetics. Users judge applications by their visual impact; ensure they feel modern, "alive," and polished through consistent spacing, interactive feedback, and platform-appropriate design. **Goal:** Autonomously implement and deliver a visually appealing, substantially complete, and functional prototype with rich aesthetics. Users judge applications by their visual impact; ensure they feel modern, "alive," and polished through consistent spacing, interactive feedback, and platform-appropriate design.
${newApplicationSteps(options)} ${newApplicationSteps(options)}
${renderReflectionWorkflow(options.enableReflection)}
`.trim(); `.trim();
} }

24
packages/core/src/skills/builtin/skill-creator/SKILL.md
View File

@@ -264,6 +264,8 @@ Skip this step only if the skill being developed already exists, and iteration o
When creating a new skill from scratch, always run the `init_skill.cjs` script. The script conveniently generates a new template skill directory that automatically includes everything a skill requires, making the skill creation process much more efficient and reliable. When creating a new skill from scratch, always run the `init_skill.cjs` script. The script conveniently generates a new template skill directory that automatically includes everything a skill requires, making the skill creation process much more efficient and reliable.
**Note for In-Repo Skills:** If you are creating a skill specifically for the current repository, you should initialize it in the `.gemini/skills` directory of the repository (e.g., `--path .gemini/skills`). This allows Gemini CLI to automatically discover and use the skill without it needing to be packaged and installed globally or at the workspace level.
**Note:** Use the absolute path to the script as provided in the `available_resources` section. **Note:** Use the absolute path to the script as provided in the `available_resources` section.
Usage: Usage:
@@ -323,11 +325,15 @@ Do not include any other fields in YAML frontmatter.
Write instructions for using the skill and its bundled resources. Write instructions for using the skill and its bundled resources.
### Step 5: Packaging a Skill ### Step 5: Packaging a Skill (Optional for In-Repo Skills)
Once development of the skill is complete, it must be packaged into a distributable .skill file that gets shared with the user. The packaging process automatically validates the skill first (checking YAML and ensuring no TODOs remain) to ensure it meets all requirements: Once development of the skill is complete, it can be packaged into a distributable .skill file that gets shared with the user.
**Note:** Use the absolute path to the script as provided in the `available_resources` section. **Note for In-Repo Skills:** If you are creating a skill specifically for the current repository and it is located in the \`.gemini/skills/\` directory, you DO NOT need to package or install it. Gemini CLI automatically loads skills from this directory. You can skip to Step 7.
If you do need to package the skill for distribution:
**Note:** Use the absolute path to the script as provided in the \`available_resources\` section.
```bash ```bash
node <path-to-skill-creator>/scripts/package_skill.cjs <path/to/skill-folder> node <path-to-skill-creator>/scripts/package_skill.cjs <path/to/skill-folder>
@@ -347,15 +353,15 @@ The packaging script will:
- Description completeness and quality - Description completeness and quality
- File organization and resource references - File organization and resource references
2. **Package** the skill if validation passes, creating a .skill file named after the skill (e.g., `my-skill.skill`) that includes all files and maintains the proper directory structure for distribution. The .skill file is a zip file with a .skill extension. 2. **Package** the skill if validation passes, creating a .skill file named after the skill (e.g., \`my-skill.skill\`) that includes all files and maintains the proper directory structure for distribution. The .skill file is a zip file with a .skill extension.
If validation fails, the script will report the errors and exit without creating a package. Fix any validation errors and run the packaging command again. If validation fails, the script will report the errors and exit without creating a package. Fix any validation errors and run the packaging command again.
### Step 6: Installing and Reloading a Skill ### Step 6: Installing and Reloading a Skill
Once the skill is packaged into a `.skill` file, offer to install it for the user. Ask whether they would like to install it locally in the current folder (workspace scope) or at the user level (user scope). If you packaged the skill into a \`.skill\` file, offer to install it for the user. Ask whether they would like to install it locally in the current folder (workspace scope) or at the user level (user scope).
If the user agrees to an installation, perform it immediately using the `run_shell_command` tool: If the user agrees to an installation, perform it immediately using the \`run_shell_command\` tool:
- **Locally (workspace scope)**: - **Locally (workspace scope)**:
```bash ```bash
@@ -366,9 +372,11 @@ If the user agrees to an installation, perform it immediately using the `run_she
gemini skills install <path/to/skill-name.skill> --scope user gemini skills install <path/to/skill-name.skill> --scope user
``` ```
**Important:** After the installation is complete, notify the user that they MUST manually execute the `/skills reload` command in their interactive Gemini CLI session to enable the new skill. They can then verify the installation by running `/skills list`. **Important:** After the installation is complete, notify the user that they MUST manually execute the \`/skills reload\` command in their interactive Gemini CLI session to enable the new skill. They can then verify the installation by running \`/skills list\`.
Note: You (the agent) cannot execute the `/skills reload` command yourself; it must be done by the user in an interactive instance of Gemini CLI. Do not attempt to run it on their behalf. For in-repo skills created in \`.gemini/skills/\`, notify the user that they must execute \`/skills reload\` to enable the new skill.
Note: You (the agent) cannot execute the \`/skills reload\` command yourself; it must be done by the user in an interactive instance of Gemini CLI. Do not attempt to run it on their behalf.
### Step 7: Iterate ### Step 7: Iterate