Menu
Use when user wants to update .pre-commit-config.yaml hooks to their latest versions from GitHub
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Compare Claude Code and Codex on the same real code-change task with isolated worktrees, identical gates, transcripts, time, and cost.
Align AGENTS.md, rules, README, plans, and chronicles with the codebase; use --clean to archive obsolete task docs into ATLAS.md.
Research current best practices and turn the evidence into a clear recommendation. Use for state-of-the-art, evidence-based, optimal-approach, comparison, or pros-and-cons questions in any field.
Clarify an ambiguous or consequential change before planning or implementation when more than one sound approach exists.
Add CHANGELOG.md entries, derive them from commits, or cut a Keep a Changelog and SemVer release.
Create a user-requested Conventional Commit from the staged changes.
| name | update-precommit |
| description | Use when user wants to update .pre-commit-config.yaml hooks to their latest versions from GitHub |
| user-invocable | true |
Bump each GitHub repo: rev in .pre-commit-config.yaml to its latest tag, diff, confirm, apply.
pre-commit autoupdate is the native tool for this — prefer it when installed.gh api repos/{owner}/{repo}/releases/latest --jq .tag_name; on no release, fall back to /tags first entry.v4.6.0 → v5.0.0) and surrounding quotes ('v0.9.3' → 'v0.10.0').