Add release-please automation to a repository that uses GitHub Actions for releases or package publishing. Use when Codex needs to inspect an existing repo, install a release-please workflow, add the required manifest/config files, preserve any existing publish workflow, add a Release flow section to CONTRIBUTING.md explaining how releases work, and then tell the user which GitHub secrets and settings to add manually after the code changes are complete.
Reviews REST API design by inventorying routes, finding overlapping functionality, comparing payloads and pagination, and checking resource naming, URL structure, identifiers, errors, idempotency, and timestamps. Use when asked to review API routes, compare endpoints, find redundant or superseding operations, assess contract consistency, or run a REST API design review.
Guided tour of changes or codebase - explains how things work conceptually rather than listing changes mechanically. Use anytime you're asked to explain, review, walk through, or summarize work, branch changes, or codebase architecture.
Add, inspect, and verify GitHub PR comments, including inline comments in an existing pending (draft) review. Use when asked to comment on a GitHub pull request, add a GitHub review comment, or add a comment to a pending/draft GitHub review.
Write and edit in GOV.UK / GDS house style — plain English, active voice, front-loaded content, sentence case, and no bold or italics for emphasis. Use when writing or editing reports, research write-ups, guidance, documentation, summaries, or any prose where clarity and accessibility matter.
Use only when the user explicitly asks to use Jujutsu (jj), such as "jj commit", "commit with jj", or "jj push". Do not use for unqualified commit/push requests or Git operations.
Manages Jujutsu workspaces for isolated task execution, GitHub PR checkout, rebases, conflict resolution, and cleanup. Use when the user asks to create or switch workspaces, check out a GitHub pull request in a JJ workspace, isolate dirty working copies, rebase onto main or another revision, resolve jj workspace conflicts, or clean up temporary workspaces.
Extract Mermaid diagrams from Markdown documents or raw Mermaid files and render them to PNG or SVG. Use when a task involves fenced ```mermaid blocks, Mermaid architecture diagrams in docs, or reliable image export where browser and Mermaid CLI configuration can be fragile.
Plain text files in a repository that tell a coding agent how the project works: commands to run, conventions to follow and things to avoid. CLAUDE.md, AGENTS.md, cursor rules and skills are the common kinds.
CLAUDE.md or AGENTS.md?
CLAUDE.md is read by Claude Code. AGENTS.md is an open format that Codex, Cursor and other agents read. Many projects keep one and point the other at it.
What is a skill?
A folder with a SKILL.md that describes one capability, such as filling PDFs or reviewing code. The agent loads it only when the task calls for it.
Can I search my own team's files too?
Your agents already can, over MCP, limited to the files you're allowed to read. Searching them from this page is coming.