Stage a finished local feature, run local verification, create a Conventional Commit, then send it through the no-mistakes gated review/fix loop before real upstream push/PR. Use when the user says a feature is done, asks for a professional stage-review flow, wants Codex to git add and commit safely, or wants no-mistakes review/verify/fix before pushing to origin.
npx skills add https://github.com/instructa/agent-skills --skill stage-review
Use this as the finished-feature workflow: inspect changes, verify locally, stage explicit files, create a Conventional Commit, push through no-mistakes, attach to the run, fix findings, rerun, and let no-mistakes perform the real upstream push/PR only after the gate passes.
git push origin in this workflow.git add .; use explicit paths or the bundled script's --all only after the user explicitly wants all current changes included.git push no-mistakes.feat|fix|refactor|build|ci|chore|docs|style|perf|test..no-mistakes.yaml, justfile, package.json, Makefile, go.mod, Cargo.toml, or equivalent project config.Resolve scripts/stage_review.py relative to this skill folder, then run:
python3 <skill-dir>/scripts/stage_review.py --cwd . plan
python <skill-dir>/scripts/stage_review.py --cwd . plan
Also run:
git status --short --branch
git diff --stat
Stop and ask if:
origin existsno-mistakes remote exists and no-mistakes init has not been approvedRun the repo's real local checks before staging. Prefer explicit commands from .no-mistakes.yaml:
commands:
test: "..."
lint: "..."
format: "..."
If no config exists, inspect repo-local command surfaces and choose the canonical one. Examples:
just test, just lint, just fmtmake test, make lint, make fmtpnpm test, pnpm lint, pnpm typecheckgo test ./..., go vet ./...cargo test, cargo clippy --all-targets -- -D warningsDo not commit if relevant local checks fail unless the user explicitly wants a broken checkpoint.
Pick the Conventional Commit subject from the actual diff:
feat(scope): concise summary
fix(scope): concise summary
refactor(scope): concise summary
Stage explicit files:
python3 <skill-dir>/scripts/stage_review.py --cwd . commit \
-m "feat(scope): concise summary" \
--body "Tests: <commands run>" \
path/to/file1 path/to/file2
Use all changed files only when the user explicitly confirms all changes belong in the feature:
python3 <skill-dir>/scripts/stage_review.py --cwd . commit \
-m "feat(scope): concise summary" \
--body "Tests: <commands run>" \
--all
Confirm the exact command first:
Ready to push <branch> through no-mistakes:
git push no-mistakes <branch>
After confirmation:
git push no-mistakes <branch>
no-mistakes
For each no-mistakes finding:
rebase, review, test, document, lint, push, pr, or cino-mistakes rerun or continue/attach as appropriateUseful commands:
no-mistakes status
no-mistakes runs --limit 10
no-mistakes attach
no-mistakes rerun
Finish only when you can report:
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
Take instructa/stage-review from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.