review-staged Skill
Generate structured code review for staged files AND all branch commits since main, using Claude Code agents. Provides full PR-equivalent coverage before pushing. Published by microsoft in Agent365-devTools.
Decision snapshot
Is this a fit?
Data analysis, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Can write or update data, Write actions, Filesystem access, Shell access
Copy skill directory
2 months ago · MIT license
Confirm write permissions and scope before use. Access note: Local files. Access note: Shell access.
What is review-staged Skill?
Generate structured code review for staged files AND all branch commits since main, using Claude Code agents. Provides full PR-equivalent coverage before pushing. Published by microsoft in Agent365-devTools. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Data analysis
- Data analysis use cases
Declared skill metadata
- Source file: .claude/skills/review-staged/SKILL.md
Allowed tools declared by source
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
- Local files
- Shell access
Requirements and access
Security and permissions
Review permissions before connecting any MCP server to an agent. Pay special attention to whether it can read local files, write data, call external services, or perform destructive actions.
When to use review-staged Skill
- Use it for data analysis.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/Agent365-devTools
- Skill file: .claude/skills/review-staged/SKILL.md
What it does
Generate structured code review for staged files AND all branch commits since main, using Claude Code agents. Provides full PR-equivalent coverage before pushing.
Skill instructions
Review Staged Files Skill Generate AI-powered code review comments covering both your currently staged changes and all commits on the branch since it diverged from main. This gives the same full-branch view that Copilot and other PR reviewers see — not just what you're about to commit. Usage bash /review-staged Review staged changes + full branch diff against main /review-staged --verbose Show detailed analysis Examples: - /review-staged - Review staged changes and all branch commits not yet on main - /review-staged --verbose - Show detailed analysis with full context What this skill does 1. Checks for staged files using git diff --staged --name-only 2. Fetches staged changes using git diff --staged 3. Fetches full branch diff using git diff $(git merge-base HEAD origin/main)...HEAD — covers all commits on the branch, not just staged files. This prevents issues in prior commits from going unreviewed. 4. Combines both diffs for review: staged diff = what you're about to add; branch diff
Verified compatibility and discovery
Frequently asked questions
What is review-staged?
review-staged is a open-source AI agent skill with Copy skill directory. Generate structured code review for staged files AND all branch commits since main, using Claude Code agents. Provides full PR-equivalent coverage before pushing.
Who is review-staged best for?
review-staged is best for reusing agent instructions, scripts, and references, data analysis workflows.
How do I install review-staged?
Install or run review-staged using Copy skill directory. Check review-staged for the latest setup command.
Is review-staged actively maintained?
review-staged may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
