agentic_coding_tools

Commit and publish local GitHub work with review requests. Use when the user wants Codex to commit staged changes, stage all changes only when nothing is staged, push the current branch, and open a GitHub pull request that tags @codex and @copilot for review.

Analyze staged and unstaged git changes and refactor for readability, maintainability, and conciseness while preserving behavior. Use when the user asks to refactor recent changes, clean up work in progress, improve code quality, or review a diff for safe structural improvements.

Generate implementation TASKS.md plans from one design document or from all feature documents in a directory.

Run a phased feature-development workflow: discovery, codebase exploration, clarifying questions, architecture options, implementation, quality review, and summary. Use when a user asks for end-to-end feature delivery with strong design rigor before coding.

Convert one planning document into PRD.md, USER_FLOW.md, BACKEND_ARCHITECTURE.md, FRONTEND_DESIGN.md, and TASKS.md in fixed deterministic order with a quality gate and traceability checks.

Remove AI-generated code slop from the current branch by auditing `git diff main...HEAD` and applying minimal cleanups. Use when a user asks to de-slop a PR/branch, make code look human-written, or remove over-defensive/verbose/generated patterns without changing behavior.

Execute a full feature workflow in order by chaining feature development, test writing, feature summaries, refactor analysis, selective refactor implementation, personal code review artifacts, and review-feedback triage when feedback is available. Use when the user wants an end-to-end structured delivery process.

Triage code review feedback from chat text or a markdown file, validate each item against the codebase, produce a fix plan, and delegate implementation to subagents. Use when the user wants every review comment verified before applying fixes.

Remove AI code slop

Execute a full feature workflow by chaining feature development, tests, feature summaries, selective cleanup, personal review artifacts, and review-feedback triage when external feedback is available.

Triage code review feedback from chat text or a markdown file, validate each item against the codebase, produce a fix plan, and hand implementation to subagents. Use when the user wants every review comment verified before fixes are applied.

Alias for `feature-summary` (kept for backward compatibility)

Alias for `code-review-personal` with concise output formatting

Alias for `code-review-personal` (kept for backward compatibility)

Alias for `feature-summary` with concise future-you framing

Perform a comprehensive branch code review using `git diff main...HEAD`, feature-plan context files, and project conventions.

Create a structured summary of current branch feature work from git diff, commit history, and optional planning files.

Run a phased feature-development workflow with discovery, codebase exploration, clarifying questions, architecture options, implementation, quality review, and summary.

Generate a single PR review guide from a feature docs directory and current git change scope.

Write high-quality tests with required pre-writing analysis of logic, inputs, invariants, and failure modes.

Perform a comprehensive branch code review using `git diff main...HEAD`, feature-plan context files, and project conventions. Use when a user asks for a personal/manual PR review, quality gate, or merge-readiness assessment with severity-ranked findings and a final verdict.

Create a structured summary of current branch feature work from git diff, commit history, and optional planning files. Use when the user asks for a concise feature write-up suitable for PR context, handoff, or planning alignment.

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Codex's capabilities with specialized knowledge, workflows, or tool integrations.

Install Codex skills into $CODEX_HOME/skills from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo (including private repos).

Update project documentation to match recent implementation changes by inspecting git status, diffs, and recent commits. Use when the user asks to refresh docs after feature work and wants minimal, accurate updates without inventing behavior.

/code-review — Conduct full feature code review