name: docs description: Audit and update documentation files to match actual repo state.
Docs
You are auditing documentation in a GitHub repository and fixing any inaccuracies.
Environment
- The target repo is cloned at
o/repo/. You have read and write access. - Only modify documentation files:
AGENTS.mdand files underdocs/.
Instructions
- Read all documentation files:
AGENTS.md,docs/architecture.md,docs/work.md,docs/reflect.md,docs/conventions.md, and any other.mdfiles indocs/. - Read the actual repo structure to compare against docs:
a. List
skills/directories and theirtools/*.tlfiles. b. ReadMakefilefor targets and help text. c. Readwork.mkfor work loop targets and standalone targets. d. Readreflect.mkfor reflect loop targets. e. Read.github/workflows/for workflow definitions. - For each doc file, check:
- structure tree: does the tree in AGENTS.md match actual directories, files, and tool lists?
- usage examples: do make targets listed in usage sections actually exist?
- tool lists: do parenthetical tool lists match actual
.tlfiles in each skill'stools/directory? - phase descriptions: do phase lists (e.g. fetch → analyze → publish) match the actual make targets?
- permissions and setup: does setup info match current workflow files?
- Fix any inaccuracies by editing the doc files directly.
- Stage and commit each fix with a descriptive message.
Constraints
- Only modify
.mdfiles in the repo root ordocs/directory. - Do not modify code, tool files, makefiles, or workflows.
- Do not add speculative documentation — only document what exists.
- Be conservative: if unsure whether something is wrong, leave it alone.
Output
Write o/docs/docs.md:
# Docs
## Changes
<list of files changed and what was fixed>
## Status
<success|no-changes>
## Notes
<any remaining issues noticed but not fixed>
Skills similaires
Generateur de Documentation API
Documentation
Genere automatiquement de la documentation API OpenAPI/Swagger.
Claude CodeCursorCopilotbeginner
340
98
1,486
Rédacteur Technique
Documentation
Rédige de la documentation technique claire selon les meilleurs style guides.
claudeCursorWindsurf+1intermediate
167
48
661
Recherche de Documentation Hono
Documentation
Utilisez le CLI hono pour rechercher et consulter la documentation du framework Hono. Les commandes hono search et hono docs permettent d'accéder rapidement aux API et guides directement depuis le terminal. Cela facilite le développement avec Hono en offrant un accès immédiat à la documentation sans quitter l'environnement de travail.
Claude CodeCursorWindsurf+2beginnerSûr
0
0
54