Using aegis
Make AI coding agents architecture-aware: baseline-first, evidence-verified, drift-checked, and safe across long tasks.
npx -y skills add GanyuanRan/Aegis --skill using-aegisAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its author says it does
Copied from the file, not written here
Use when starting a turn or checking Aegis skill routing.
SKILL.md
2.4 KB, as published. Nobody here has run it
<SUBAGENT-STOP>Skip for subagents.</SUBAGENT-STOP>
<EXTREMELY-IMPORTANT> You have Aegis. Load explicit/relevant Aegis skill before response/action; otherwise proceed normally. </EXTREMELY-IMPORTANT>Hot Path
- User/project instructions outrank Aegis.
- Active codebase question/"what next": check README/ADR/rules/baseline, else
bounded index-first scan. Non-trivial owners passively use relevant
CONTEXT-MAP.md/CONTEXT.md; composeestablishing-project-contextonly on semantic delta/conflict. Create baselines only with evidence. - Direct grilling or plan/design pressure-tests (
grill me,grill this plan,审问我,盘问我,拷问我) route tobrainstorming; literal/explanatory uses do not. /aegis-goalorAegis goal:loadsgoal-framingbefore routing.- Bug, failure, regression, or unexpected behavior routes to
systematic-debugging; quick bug lane owns Change Necessity before source edits. - Classify before implementation/start/resume/compaction. Low: intent, baseline, verification. Medium/high: baseline read-set + plan. TDD: off=no auto route/load; auto=strict/light/skipped; explicit request applies. Spec Brief or Design Spec only for complex, ambiguous, contract, cross-module work; shared/core/contract/cross-module never low without evidence. Source edits/new paths: owner workflow surfaces Change Necessity.
- Non-tiny loaded skill: at the first substantive user-visible stage say why Aegis is shaping work/risk; do not wait for the user to ask. structured trace only for audit/debug/release/long-task review/asked;
Trace Digestdoes not route. Tiny stays implicit. - ArchitectureReviewRequired: yes for medium/high architecture/contract/ cross-module/owner/source-of-truth/fallback/adapter/baseline; carry to verification.
- Workspace support is lazy; use configured Aegis workspace support only when records needed. Fast Q&A/status/tiny edits write no files.
- Load smallest needed skill/reference.
- Tool/log/memory/search outputs are evidence candidates, not prompt payloads; summary first, large input index->window->excerpt.
- No history/sessions/transcripts/large logs by default; bound requested evidence by scope/time/lines.
- Unclear host tool-name mapping: read smallest relevant reference.
Contract: Route: fast-path; Aegis Reason Note.