Skip to content

mgiovani/ai-arsenal / skills/docs-update

docs-update

Verified

Refresh existing docs (architecture, onboarding, data-model, deployment, security, contributing) so they match the current codebase, verifying every claim against real code instead of guessing. Use when the user says docs are stale, asks to sync docs with recent code changes, update a specific doc file, or update a whole category (core/data/infrastructure/development) after a refactor or schema change. Not for creating docs that don't exist yet (use docs-init) or scoring/auditing doc health without editing (use docs-check).

FileKindSize
SKILL.mdskill md7.8 KB
evals/evals.jsonconfig2.7 KB
evals/trigger-eval.jsonconfig1.9 KB
references/change-detection.mdmarkdown1.6 KB
references/update-strategies.mdmarkdown2.3 KB

evals/trigger-eval.json

View on GitHub
[
  {"query": "our docs are stale after the refactor, can you sync them with the code", "should_trigger": true},
  {"query": "update docs/architecture.md to match the new microservices split", "should_trigger": true},
  {"query": "run docs-update on category:core", "should_trigger": true},
  {"query": "the onboarding doc mentions commands that no longer exist, please fix it", "should_trigger": true},
  {"query": "update data-model.md after the schema migration", "should_trigger": true},
  {"query": "docs-update all", "should_trigger": true},
  {"query": "regenerate deployment docs now that we moved to k8s", "should_trigger": true},
  {"query": "refresh contributing.md, the workflow changed", "should_trigger": true},
  {"query": "our architecture doc is out of sync with the new payment service, update it", "should_trigger": true},
  {"query": "sync the docs with the schema changes we just made", "should_trigger": true},
  {"query": "create the initial docs/ structure for this new project", "should_trigger": false},
  {"query": "audit our docs and tell me what's stale, don't change anything", "should_trigger": false},
  {"query": "does docs/architecture.md still match the actual services we have? just check, don't edit", "should_trigger": false},
  {"query": "generate a Mermaid diagram of the service architecture", "should_trigger": false},
  {"query": "write an ADR for switching to event sourcing", "should_trigger": false},
  {"query": "draft an RFC proposing we move to a monorepo", "should_trigger": false},
  {"query": "bootstrap documentation for this brand new repo from scratch", "should_trigger": false},
  {"query": "review this PR for correctness and style before I merge", "should_trigger": false},
  {"query": "write a conventional commit message for these staged changes", "should_trigger": false},
  {"query": "check if our onboarding doc is missing any required sections", "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: 471kUpdated 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: 471kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 471kUpdated 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