القائمة
Deep-mine the source code to discover implemented features; writes ai/analysis/FEATURE_CATALOG.md.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | create-feature-catalog |
| description | Deep-mine the source code to discover implemented features; writes ai/analysis/FEATURE_CATALOG.md. |
| disable-model-invocation | true |
Build the feature catalog — the highest-value artifact for agents. Budget significant
exploration; use repo-explorer for the heavy reading.
ai/analysis/FEATURE_CATALOG.mdFor every feature: name · business goal (one line) · touch list per layer · verifying tests · related features. End with two sections agents use most:
[inferred]. Where a layer can't be confirmed, write "UNSURE".ai/guide/FEATURE_MAP.md candidate list to reference
the catalog, nothing more.Bootstrap the ai/ knowledge layer for a repo that has none — draft the MODULE_MAP, diagrams, and guide docs as [inferred] for a human to audit, touching no source code. Use when the maps are still placeholders or the user asks to cold-start, bootstrap, or onboard a repository.
Bootstrap the ai/ knowledge layer for a repo that has none — draft the MODULE_MAP, diagrams, and guide docs as [inferred] for a human to audit, touching no source code. Use when the maps are still placeholders or the user asks to cold-start, bootstrap, or onboard a repository.
Deep, judgement-based adversarial code audit — hunts for stale cross-references, unescaped interpolation, platform gaps, generated-file ownership conflicts, and cross-module consistency rot that no mechanical check can catch. Read-only; writes a dated findings report.
Kit-maintainer diagnostic (LOCAL-ONLY, not distributed) that audits the README and docs/ for staleness against the repo's real command/skill/CLI roster, stamped tree, and cross-doc consistency. Read-only; produces a severity-ranked findings report.
Run verification and drift checks on the AI knowledge-base to identify missing documentation or stale references.
Implement a spec from ai/lab/specs/ exactly as written — zero design decisions, stop-and-report on any spec-vs-reality conflict, tests are the definition of done. Built for lighter implementation models.