Menú
Use when updating docs, syncing CLAUDE.md, AGENTS.md, or README.md, fixing stale documentation, or refreshing project rules and skills. Keeps docs aligned with code changes.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
| name | update-project |
| description | Use when updating docs, syncing CLAUDE.md, AGENTS.md, or README.md, fixing stale documentation, or refreshing project rules and skills. Keeps docs aligned with code changes. |
| license | MIT |
| allowed-tools | Read Glob Edit Write Bash(git:*) |
| model | haiku |
| effort | low |
| compatibility | Any project with agent docs (CLAUDE.md/AGENTS.md) and/or a README; language-agnostic |
| metadata | {"short-description":"Keep docs in sync with code."} |
You keep project documentation synchronized with recent code changes and git commits.
Run after significant code changes, before a release, or whenever docs may be stale.
Update only what the project actually changed. Verify a claim against the tree before you write it, and leave sections you cannot verify alone.
Detect which agent the project targets and maintain its instruction file accordingly: CLAUDE.md (Claude Code), AGENTS.md (Codex, OpenCode, and the cross-agent standard), or both. Component directories follow the same split — .claude/ for Claude Code, .agents/ for the cross-agent convention.
| Rule | Impact | File |
|---|---|---|
| Agent docs (CLAUDE.md / AGENTS.md / README.md) | HIGH | rules/agent-docs.md |
| Components (agents, skills, rules) | MEDIUM | rules/components.md |
git log --oneline -20 and git diff to identify recent changesCLAUDE.md, AGENTS.md) and whether README.md exists (create if missing).claude/ and .agents/ for agents/*.md, skills/*/SKILL.md, and rules/*.md filesRead the relevant rule file and apply updates:
rules/agent-docs.md for CLAUDE.md / AGENTS.md / README.md changesrules/components.md for .claude/ or .agents/ agents, skills, and rules changesUse when refactoring, cleaning up code, reducing complexity, fixing code smells, or improving code quality. Audits code for dead code, nesting, and patterns.
Use when writing tests, running tests, adding test coverage, or debugging test failures. Detects the language and its test runner (JS/TS, Python, Go, Rust) for unit and component testing.
Use when committing changes, staging files, saving work, or making a git commit. Creates clean commits in the repository's own convention (conventional commits, area prefix, tracker ID, or plain) with secret scanning (GitLeaks).
Use when creating a branch, starting work on an issue, or checking out a new feature branch. Validates branch naming and links to GitHub issues automatically.
Use when opening a PR, submitting for review, pushing a branch, or creating a pull request. Pushes and creates GitHub PRs with auto-assignment and description.
Use when hardening a dependency supply chain, pinning versions, adding registry/security flags, or setting up Renovate. Detects the language and locks down install scripts, versions, and CI checks (JS/TS, Python, Go, Rust).