mgiovani/ai-arsenal / skills/docs-update
docs-update
VerifiedRefresh 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).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 7.8 KB |
| evals/evals.json | config | 2.7 KB |
| evals/trigger-eval.json | config | 1.9 KB |
| references/change-detection.md | markdown | 1.6 KB |
| references/update-strategies.md | markdown | 2.3 KB |
references/change-detection.md
View on GitHub# Change detection
Fallback commands for detecting codebase changes when the primary freshness check
(SKILL.md Phase 2) can't run: no `.git`, the doc is untracked, or it's a first commit.
Replace `<doc-path>` with the actual resolved path from Phase 1 (e.g. `docs/architecture.md`),
never hardcode a specific document here, this file backs every doc type.
## General change detection
```bash
# Find modified source files in the last 7 days
git diff --name-only HEAD@{7.days.ago}..HEAD 2>/dev/null | grep -E "\.(py|ts|js|java|go)$" | head -20
# Check for new files added in the last 7 days
git log --since="7 days ago" --diff-filter=A --name-only --pretty=format: | sort -u | head -20
```
## Per-document freshness check
```bash
# When was this specific doc last modified? (empty output = untracked or doesn't exist yet)
git log -1 --format="%ai" -- <doc-path> 2>/dev/null
# No git history for the doc at all — fall back to a fixed lookback window
git log --since="7 days ago" --oneline --name-only | head -50
```
## Technology stack detection
```bash
# Check for language/framework
find . -name "package.json" -o -name "pyproject.toml" -o -name "go.mod" -o -name "Cargo.toml" | head -5
# Check for database
find . -name "*models.py" -o -name "*schema.prisma" -o -name "*entity.ts" | head -5
# Check for infrastructure
find . -name "Dockerfile" -o -name "docker-compose.yml" -o -name "*.k8s.yaml" | head -5
```
## Load templates
Template location: `../docs-init/assets/templates/` (shared with docs-init, see SKILL.md
Phase 4 for the standalone-install fallback). Load the template matching the doc being
updated for consistent formatting across creation and updates.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 471k | Updated | Claude CodeCodex | Verified | Install |
| 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: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |