菜单
Review local code changes organized into logical chapters with Stage CLI, a code review tool that works with any AI agent
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/Aradotso/devtools-skills --skill stage-cli-code-review命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
基于 SOC 职业分类
| name | stage-cli-code-review |
| description | Review local code changes organized into logical chapters with Stage CLI, a code review tool that works with any AI agent |
| triggers | ["review my code changes in chapters","organize my git diff into reviewable sections","show me staged changes with stage cli","create a code review with stage","break down my local changes for review","review code changes by chapter","use stage to review uncommitted work","open stage review interface"] |
Skill by ara.so — Devtools Skills collection.
Stage CLI is a code review tool that organizes local code changes into logical chapters and highlights what to review. It runs entirely on your local machine and works with any AI agent to help you review code before committing or creating pull requests.
Install globally via npm:
npm install -g stagereview
Or use directly with npx:
npx stagereview
Review your current changes (auto-detects what to review):
stage-chapters
This will:
Review only changes that are staged for commit:
stage-chapters --ref staged
Review only unstaged working directory changes:
stage-chapters --ref unstaged
Review staged + unstaged + untracked files:
stage-chapters --ref work
Compare your changes against a specific base branch:
stage-chapters --base develop
stage-chapters --base feature/authentication
stage-chapters --base origin/main
Before committing, review staged changes:
git add .
stage-chapters --ref staged
Review all changes in your feature branch against main:
stage-chapters --base main --ref work
Review what you've changed since last commit:
stage-chapters --ref unstaged
Compare your current branch against another feature branch:
stage-chapters --base feature-a
--base <ref>Specifies the base git reference to diff against.
main, master, or developExamples:
--base main
--base origin/develop
--base abc123f
--base v1.2.0
--ref <mode>Defines the scope of changes to review.
Options:
work - All local changes (staged + unstaged + untracked)staged - Only changes in git staging areaunstaged - Only working directory changes not stagedExamples:
--ref work
--ref staged
--ref unstaged
Stage CLI is designed to work seamlessly with AI coding agents. In your agent's chat interface:
/stage-chapters
Or with options:
/stage-chapters --ref staged --base develop
The agent can help you:
While Stage CLI is primarily a command-line tool, you can integrate it into scripts:
#!/bin/bash
# Review script for CI/local checks
# Check if there are staged changes
if git diff --cached --quiet; then
echo "No staged changes to review"
exit 0
fi
# Run Stage review
stage-chapters --ref staged
#!/bin/bash
# Pre-push review workflow
MAIN_BRANCH="main"
CURRENT_BRANCH=$(git rev-parse --abbrev-ref HEAD)
if [ "$CURRENT_BRANCH" != "$MAIN_BRANCH" ]; then
echo "Reviewing changes against $MAIN_BRANCH..."
stage-chapters --base $MAIN_BRANCH
fi
Stage CLI organizes changes into logical chapters based on:
The browser UI shows:
Stage CLI requires a git repository. Initialize one:
git init
Verify you have changes:
git status
If using --ref staged, ensure files are staged:
git add <files>
Ensure the base reference exists:
git branch -a # List all branches
git log --oneline # Check commit history
Use a valid reference:
stage-chapters --base origin/main
Stage CLI starts a local web server. If the port is occupied, it will try alternative ports automatically. Close any conflicting applications if issues persist.
For very large changesets, consider:
stage-chapters --ref staged # Review staged first
stage-chapters --ref unstaged # Then unstaged
Manually open the URL shown in terminal output (typically http://localhost:3000 or similar).
Run Stage reviews before commits, not just before PRs:
# After making changes
git add -p # Interactively stage
stage-chapters --ref staged # Review staged
git commit
Match the --ref option to your workflow:
--ref staged--ref unstaged--ref work --base mainUse chapters to:
Let the AI agent analyze Stage's output:
Review the chapters from Stage CLI and identify:
1. Potential bugs or edge cases
2. Missing error handling
3. Inconsistent patterns
Before creating a pull request:
# Ensure all changes are committed
git add -A
git commit -m "Feature complete"
# Review full feature against main
stage-chapters --base main
# Address review findings
# Create PR
Stage reviews all changes, but you can prepare specific changes:
# Stage only TypeScript files
git add '*.ts'
stage-chapters --ref staged
# Stage specific directory
git add src/components/
stage-chapters --ref staged
Compare changes across multiple branches:
# Review branch A vs main
git checkout feature-a
stage-chapters --base main
# Review branch B vs main
git checkout feature-b
stage-chapters --base main
Add to .git/hooks/pre-commit:
#!/bin/bash
# Launch Stage review before commit
stage-chapters --ref staged
read -p "Proceed with commit? (y/n) " -n 1 -r
echo
if [[ ! $REPLY =~ ^[Yy]$ ]]; then
exit 1
fi
The full Stage experience on the website offers additional features like team collaboration, persistent reviews, and integration with GitHub pull requests.