Update repo documentation and agent-facing guidance such as AGENTS.md, README.md, docs/, specs, plans, and runbooks. Use when code, skill, or infrastructure changes risk doc drift or when documentation needs cleanup or restructuring. Do not use for code review, runtime verification, or `agent-readiness` setup.
98
100%
Does it follow best practices?
Impact
94%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
The backend team at Fieldstone Labs recently completed a major refactor of their invoicing-service. Over three sprints they renamed scripts, moved configuration files, restructured the API, and removed a feature. The code is in good shape, but nobody updated the docs. Now the DevOps team is getting paged because new engineers are running commands from AGENTS.md and README.md that no longer exist, and the on-call runbook references an endpoint that was deleted in the refactor.
Your job is to audit the documentation against the actual repository state, identify every stale reference, and fix the documentation so it accurately reflects what's really in the codebase. Be systematic — don't just fix what looks obviously wrong, check every command and file path mentioned in the docs against what actually exists.
Produce the following:
doc-audit.md — a structured report listing every stale reference found, what it pointed to, what it actually should point to (or that it should be removed), and confirmation that you verified the correct target existsDo not fix anything you haven't verified — if you're not sure whether a path is correct, say so in the audit report.
The following files are provided as inputs. Extract them before beginning.
=============== FILE: inputs/AGENTS.md ===============
Boot the service:
./scripts/bootstrap.shRun tests:
npm testRun integration tests:
npm run test:integrationsrc/utils/logger.ts for all loggingsrc/lib/calculator.tsconfig/app.yaml — never hardcode valuesnpx knex migrate:latest=============== FILE: inputs/README.md ===============
REST API for invoice generation and payment tracking.
npm install
cp config/app.yaml.example config/app.yaml./scripts/bootstrap.sh
npm run devSee CONTRIBUTING.md.
=============== FILE: inputs/docs/ops/runbook.md ===============
Check the service logs:
docker logs invoicing-service --tail 100Verify the calculator is healthy by calling the health endpoint:
curl http://localhost:3000/api/v2/healthThe invoice PDF export feature uses wkhtmltopdf. If PDFs aren't generating:
which wkhtmltopdf./scripts/test-pdf.shcat logs/pdf-errors.logIf the feature is completely broken, you can disable it temporarily by setting DISABLE_PDF_EXPORT=true in the environment.
Webhook processing is handled by src/api/webhooks.ts. Common causes:
STRIPE_WEBHOOK_SECRET in environment/api/v2/webhooks/stripe is accessibleDATABASE_URL and run npx knex migrate:latest=============== FILE: inputs/repo-manifest.json =============== { "_comment": "This file represents the actual current state of the repository after refactoring.", "scripts": { "exists": ["setup.sh", "seed.sh", "migrate.sh"], "removed": ["bootstrap.sh", "test-pdf.sh"] }, "config": { "exists": ["config/settings.yaml", "config/settings.yaml.example"], "removed": ["config/app.yaml", "config/app.yaml.example"] }, "src": { "exists": [ "src/utils/logger.ts", "src/lib/calculator.ts", "src/api/webhooks.ts", "src/api/invoices.ts", "src/api/payments.ts" ], "removed": [] }, "docs": { "exists": [ "docs/architecture.md", "docs/api-v3.md", "docs/ops/deploy.md", "docs/ops/runbook.md" ], "removed": ["docs/api-v2.md"] }, "api_endpoints": { "exists": ["/api/v3/health", "/api/v3/invoices", "/api/v3/payments", "/api/v3/webhooks/stripe"], "removed": ["/api/v2/health", "/api/v2/webhooks/stripe"] }, "features": { "removed": ["PDF export — feature was cut from v3 scope"] } }