Menú
Fetch an issue from the upstream repository, understand its scope, map it to existing skills, and produce an implementation plan
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Step-by-step checklist for adding a new CLI flag to openshell-image-builder, covering all locations from the clap struct to integration tests
Understand and edit the OpenShell sandbox policy — base YAML, network rule schema, how inference and agent fragments are merged, and how to test changes
Step-by-step checklist for adding a new inference provider to openshell-image-builder, covering the trait implementation, agent wiring, unit tests, integration tests, and README
Step-by-step checklist for adding a new agent to openshell-image-builder, covering the Agent trait, mod.rs registration, unit tests, integration tests, and README
Step-by-step checklist for adding a new base image to openshell-image-builder, covering the Containerfile match arm, unit tests, and integration tests
Create a new project skill in .agents/skills/ and register it in the skills README
| name | work-on-issue |
| description | Fetch an issue from the upstream repository, understand its scope, map it to existing skills, and produce an implementation plan |
| argument-hint | <issue-id> |
Fetch an upstream issue and turn it into a concrete implementation plan.
git remote get-url upstream
Extract the owner/repo slug from the URL. Both HTTPS and SSH forms are valid:
https://github.com/owner/repo.git → owner/repogit@github.com:owner/repo.git → owner/repogh issue view <issue-id> --repo <owner/repo> --comments
Read the full output: title, body, labels, and every comment. If the issue references other issues or PRs, fetch those too:
gh issue view <other-id> --repo <owner/repo> --comments
gh pr view <pr-id> --repo <owner/repo> --comments
Identify what kind of change the issue is asking for, then check whether an existing skill already covers this type of work:
| If the issue asks for… | Use skill |
|---|---|
| A new supported base OS image | /add-base-image |
| A new CLI flag or option | /add-cli-flag |
| A new inference provider | /add-inference |
| A new agent | /add-agent |
| A new sandbox network rule | /sandbox-policy |
If an existing skill applies, load it — it lists every file that needs to change and the exact patterns to follow.
Read the source files most likely affected by the issue. Use grep, find, and Read to locate the relevant functions, structs, and tests. Do not skip this step — the plan must name specific files and line ranges, not describe changes in the abstract.
Call EnterPlanMode and write a concrete implementation plan that covers: