Skip to content
Back to skills

Act Audit Docs

ASecurity

Use after a feature wave, before a handover, or when docs/project might be stale or contradict the code (architecture, coding rules, testing, features, decisions). Brings outdated entries in line with the actual code. Not for template drift - use act-doctor.

  • 3 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added October 8, 2026
ai-agentsgotestinggit

Security analysis

A100/100

Scanned October 8, 2026

npx -y skills add wrufeger/agentic-coding-template --skill act-audit-docs --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Act Audit Docs?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Act Audit Docs
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/wrufeger-act-audit-docs/badge)](https://www.skillsdirectory.com/skills/wrufeger-act-audit-docs)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: act-audit-docs
description: Use after a feature wave, before a handover, or when docs/project might be stale or contradict the code (architecture, coding rules, testing, features, decisions). Brings outdated entries in line with the actual code. Not for template drift - use act-doctor.
---

# Audit docs/project against the code

`docs/project/` describes the actual state, not the plan — this skill closes the gap between the
two. Whether the project still matches the template's own `.act/` is a separate concern, covered
by `act-doctor`.

1. `git status` and `git diff --stat -- docs/project`: sight open changes from earlier sessions
   first.
2. Run each pair in sequence, not in parallel: `explorer` first — what actually exists — modules,
   endpoints, tables, commands, tests — each claim backed by `<path>:<line>` (`R-role-worker`);
   then `doc-writer` compares that report against `docs/project/*` and corrects it directly. On a
   larger project, one such pair per doc area — those pairs may run in parallel with each other,
   never explorer and doc-writer within the same pair.
3. Fold in what the wave produced: a new interface or table into `architecture.md`/`features.md`,
   a newly learned convention into `coding_rules.md`, changed tests into `testing.md`, a severe
   failure into `docs/project/incidents/`. Maintaining `testing.md`: check that the runner it names
   actually exists and that its command isn't interactive (no unattended install prompt), same
   check as before any test run (`.act/agents/builder.md`).
4. `doc-writer` updates `docs/README.md` (index, data-as-of dates).

A full pass across all doc areas logs a journal entry whose title starts with `act-audit-docs`
(`entries.py new ledger "act-audit-docs: ..."`); a spot check of one area skips the entry — this is
how session start tells how long ago the last full pass ran.

## Limits

Nothing here touches code. A finding that needs a code change becomes a task, not a doc edit
worked around it. No doc entry without a code check first — docs describe the actual state, never
the wish (`R-work-evidence`).

Close with `act-commit`.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.