Borrowing it
Nothing to install: this file belongs to EchoingVesper/mcp-task-orchestrator. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/EchoingVesper/mcp-task-orchestrator/main/.claude/commands/code-quality/review-staged-unstaged.mdgit clone --depth 1 https://github.com/EchoingVesper/mcp-task-orchestratorWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/echoingvesper/mcp-task-orchestrator/review-staged-unstaged)<a href="https://agentmods.dev/commands/echoingvesper/mcp-task-orchestrator/review-staged-unstaged"><img src="https://agentmods.dev/badge/commands/echoingvesper/mcp-task-orchestrator/review-staged-unstaged/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/echoingvesper/mcp-task-orchestrator/review-staged-unstaged"><img src="https://agentmods.dev/badge/commands/echoingvesper/mcp-task-orchestrator/review-staged-unstaged.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.00540 |
| Opus 5 | $0.00000 | $0.00270 |
| Sonnet 5 | $0.00000 | $0.00108 |
| Haiku 4.5 | $0.00000 | $0.00054 |
Grade A, and why
review-staged-unstaged scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
This is a copy
86% identical to review-general — 18 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
List and review any files in the staging area, both staged and unstaged. Ensure you look at both new files and modified files.
Check the diff of each file to see what has changed.
Previous review report: $ARGUMENTS
May or may not be added, ignore the previous review if not specified.
Review Focus Areas
-
Code Quality
- Type hints on all functions and classes
- Pydantic v2 models for data validation
- No print() statements (use logging)
- Proper error handling
- Following PEP 8
- Docstrings following google style python docstrings
-
Pydantic v2 Patterns
- Using ConfigDict not class Config
- field_validator not @validator
- model_dump() not dict()
- Proper use of Annotated types
-
Security
- Input validation on all endpoints
- No SQL injection vulnerabilities
- Passwords properly hashed
- No hardcoded secrets
-
Structure
- Unit tests are co-located with the code they test in tests/ folders
- Each feature is self-contained with its own models, service, and tools
- Shared components are only things used by multiple features
- Future improvements (like multiple AI providers) would go in src/shared/ai_providers/ when implemented
- Integration tests remain at the root level in tests/integration/
-
Linting
- ruff check --fix
- mypy
-
Testing
- New code has tests
- Edge cases covered
- Mocking external dependencies
-
Performance
- No N+1 queries
- Efficient algorithms
- Proper async usage
-
Documentation
- Clear README with setup instructions
- CLAUDE.md is up to date with any new important utils, dependencies etc for future cluade code instances
Review Output
Create a concise review report with:
# Code Review #[number]
## Summary
[2-3 sentence overview]
## Issues Found
### 🔴 Critical (Must Fix)
- [Issue with file:line and suggested fix]
### 🟡 Important (Should Fix)
- [Issue with file:line and suggested fix]
### 🟢 Minor (Consider)
- [Improvement suggestions]
## Good Practices
- [What was done well]
## Test Coverage
Current: X% | Required: 80%
Missing tests: [list]
Save report to PRPs/code_reviews/review[#].md (check existing files first)
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 10d ago First seen · 86 lines · 0 tokens per session scan A 6950ffd6a997
review-staged-unstaged is a command published in the GitHub repository EchoingVesper/mcp-task-orchestrator (28 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 540 tokens. A static security scan graded it A with 0 findings. It is 86% identical to review-general, differing in 18 lines, and is treated as a copy.
Other commands, from other repositories
review-branch
Review an existing branch holistically before merging — blast radius, conventions, security, and spec compliance.
pr
Open a Pull Request on GitHub following team conventions. Draft by default.
pr-manager
Comprehensive pull request management with ruv-swarm coordination for automated reviews, testing, and merge workflows.
generate-linear-worklog
You are tasked with generating a technical work log comment for a Linear issue based on recent git commits.
add-changelog
Generate and maintain project changelog.
git-status
Command "git-status" from qdhenry/Claude-Command-Suite, covering git status command and instructions.