Skip to content

mgiovani/ai-arsenal / skills/docs-init

docs-init

Verified

Bootstraps a documentation structure (architecture, onboarding, data-model, deployment, security, contributing, and a first ADR) for a project that has little or no docs/ directory, exploring the codebase and populating templates only with content evidenced in the code. Use when the user wants to set up docs, bootstrap documentation, initialize project docs, scaffold a docs/ folder, or create docs from scratch for a new or undocumented project. Not for refreshing or syncing docs that already exist (use docs-update). Not for generating a standalone architecture or ER diagram without the surrounding document (use docs-diagram).

evals/trigger-eval.json

View on GitHub
[
  {"query": "set up docs for this project, there's nothing in docs/ yet", "should_trigger": true},
  {"query": "bootstrap documentation for my repo from scratch", "should_trigger": true},
  {"query": "initialize project docs — we've never had any", "should_trigger": true},
  {"query": "create docs from scratch for this codebase", "should_trigger": true},
  {"query": "this project has no docs/ folder, can you create one with architecture and onboarding docs", "should_trigger": true},
  {"query": "docs-init for a Python FastAPI microservice", "should_trigger": true},
  {"query": "scaffold a documentation structure for this repo", "should_trigger": true},
  {"query": "we need onboarding, architecture, and contributing docs — nothing exists yet", "should_trigger": true},
  {"query": "generate a full docs/ folder for this new Next.js app, we haven't documented anything", "should_trigger": true},
  {"query": "kick off documentation for this undocumented service", "should_trigger": true},
  {"query": "our docs are out of date, sync them with the current code", "should_trigger": false},
  {"query": "refresh the architecture doc after the refactor we just did", "should_trigger": false},
  {"query": "update docs/deployment.md to match the new CI pipeline", "should_trigger": false},
  {"query": "generate an ER diagram for our database", "should_trigger": false},
  {"query": "create an architecture diagram in mermaid", "should_trigger": false},
  {"query": "score our documentation health and tell me what's stale", "should_trigger": false},
  {"query": "check if our docs are complete and up to date", "should_trigger": false},
  {"query": "write an ADR for switching to Postgres", "should_trigger": false},
  {"query": "draft an RFC for the new auth system", "should_trigger": false},
  {"query": "write a conventional commit message for these changes", "should_trigger": false}
]
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 470kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 470kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 470kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall