菜单
Use when handed a GitHub issue (number or URL) to execute end to end. Reads the issue, classifies the work, loads the matching workflow skill, runs it against the stated acceptance criteria, and reports results without performing any git operations.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when cutting a release of the aegis-stack package. Covers the version-bump file set, the changelog cut, the three release gates, TestPyPI rc verification, and the tag-push mechanics that trigger the publish workflow.
Use when adding a new HTTP endpoint to this project's FastAPI backend. Covers the router module, request and response schemas, dependency wiring, router registration, the health surface, and the API test.
Use when adding a command to this project's own CLI (the app CLI under app/cli/, not the aegis tool). Covers the command module, Typer registration, the sync-plus-asyncio.run rule, and i18n strings.
Use when adding or changing a database model in this project. Covers the SQLModel table definition, the alembic autogenerate migration flow, and the query rules that keep access performant.
Use when adding a job that runs on a schedule (periodic or at a fixed time) in this project. Covers writing the task function and registering it with the scheduler.
Use when adding or removing a capability (a component or service) in this project, or pulling framework updates. Covers the aegis add, remove, and update commands and what each one changes.
| name | execute-issue |
| description | Use when handed a GitHub issue (number or URL) to execute end to end. Reads the issue, classifies the work, loads the matching workflow skill, runs it against the stated acceptance criteria, and reports results without performing any git operations. |
Turn a detailed GitHub issue into an executed change. This skill is the router:
it does not itself know how to add a service or cut a release, it classifies the
work and hands off to the workflow skill that does, then holds the run to the
issue's acceptance criteria. Issues authored with the agent-task template
(.github/ISSUE_TEMPLATE/agent-task.yml) map field-for-field onto this run.
Use when given an issue number or URL and asked to execute, implement, or "do" it.
Do NOT use to triage, comment on, or plan an issue without implementing it, and do NOT use it to open, branch, commit, or PR anything (those stay human-triggered; see Pitfalls). If the issue is vague enough that the scope or acceptance criteria cannot be restated concretely, stop and ask rather than guess.
This skill owns no fixed file list. The files that change are whatever the classified workflow skill dictates. Reading order:
gh issue view <n> --comments)..claude/skills/<name>/SKILL.md, whose
## Files that change section is the authoritative list for the run.Classification map (issue work type to skill):
add-service*_backend option): add-componenti18naegis tool CLI: add-cli-commandreleasetemplate-devAn issue may span more than one type (a service that adds a CLI command and locale strings). Load every matching skill and follow each for its slice.
gh issue view <n> --comments. Read the comments; they often
correct the body (a burned-rc note, a moved file). Where a comment and the
body disagree, the comment usually wins, but verify against the code.## Files that change,
## Procedure, ## Gates, and ## Pitfalls.The gates are whichever the loaded workflow skill specifies (for example
make check plus a test-stacks or test-template target). Run exactly those;
do not substitute a lighter target for the one the skill names as the
before-done gate.