Menü
Explicit-only. Audit Markdown docs for static accuracy and cross-document consistency against the repo, fixing what is safe. Excludes memory files by default.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Explicit-only. Run a named autonomous mode, repeatedly selecting, implementing, and shipping coherent work while preserving anything blocked.
Use globally installed `playwright-cli` for browser automation, UI inspection, screenshots, Playwright test debugging, or test generation. Trigger when a task needs browser interaction or test repair. Do not use for generic tests, web search, non-browser docs, or API-only work.
Explicit-only. Align a feature specification, produce a reviewed plan, complete the local work, and ship the pull request.
Explicit-only. Review a plan/task/context artifact set and report material findings.
Explicit-only. Ship one pull request, observe hosted CI and review feedback, follow PR policy, reply to every eligible comment, and request merge authorization before merging and cleaning up.
Explicit-only. Verify completed work against its authoritative contract and report coverage, working-code evidence, material gaps, and the completion verdict.
| name | audit-documentation |
| description | Explicit-only. Audit Markdown docs for static accuracy and cross-document consistency against the repo, fixing what is safe. Excludes memory files by default. |
Audit Markdown against repository evidence; fix safe inaccuracies.
*.md files./audit-memory when the user requests memory files.no-findings.Record scope and inspect enough context to establish its claims. For large scopes, parallelize non-overlapping read-only investigations; the owning agent validates candidates, resolves conflicts, and edits.
Check:
Mark statically indeterminate claims unverified. Ignore style, fix supported inaccuracies, and leave code gaps or unresolved intent unchanged. Do not log the audit to memory.
Write a concise summary with:
# Documentation Audit Summary — scope and verdict## Fixes Applied## Code Gaps## Decisions NeededFindings include severity, location, evidence, impact, outcome (fixed,
code-gap, or needs-user-decision), and type (command, path, config,
interface, architecture, or cross-doc). Use None for empty sections.
Finish when every document is checked and every material finding has an outcome.