Borrowing it
Nothing to install: this file belongs to klapaudius/symfony-mcp-server. 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/klapaudius/symfony-mcp-server/master/.claude/commands/pre-commit-review.mdgit clone --depth 1 https://github.com/klapaudius/symfony-mcp-serverWrote 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/klapaudius/symfony-mcp-server/pre-commit-review)<a href="https://agentmods.dev/commands/klapaudius/symfony-mcp-server/pre-commit-review"><img src="https://agentmods.dev/badge/commands/klapaudius/symfony-mcp-server/pre-commit-review/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/klapaudius/symfony-mcp-server/pre-commit-review"><img src="https://agentmods.dev/badge/commands/klapaudius/symfony-mcp-server/pre-commit-review.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.00394 |
| Opus 5.5 | $0.00000 | $0.00158 |
| Sonnet 5.5 | $0.00000 | $0.00079 |
| Haiku 4.5 | $0.00000 | $0.00039 |
Grade A, and why
pre-commit-review 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 2mo 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.
How it starts
The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Instructions: pre-commit-review
Please perform a comprehensive code review for the uncommited changes. Follow these steps:
1. Code Quality Review
Analyze all changes and evaluate:
Architecture & Design:
- Does the code follow Symfony >6.4 best practices and conventions?
- Does the code follow single responsibility principle with clear separation of concerns?
- Are new dependencies justified and properly integrated?
Security & Performance:
- Are there any security vulnerabilities or exposed sensitive data?
- Is caching implemented where beneficial?
- Does memory usage is optimal?
Code Standards:
- Does the code follow PSR standards and project conventions?
- Are variable names and methods descriptive and consistent?
- Is error handling comprehensive and appropriate?
- Are comments and documentation adequate?
- Does all methods have a PHPDocs block?
- Does test method's names are snake_case_named?
Testing & Reliability:
- Are unit tests present for the new functionality?
- Do integration tests cover the main workflows?
- Are edge cases and error scenarios tested?
- Is the test coverage adequate?
2. Risk Assessment
Identify potential risks:
- Breaking changes that might affect existing functionality
- Database migration requirements
- Performance impact on large datasets
- Compatibility issues with external integrations
3. Recommendations
Provide specific, actionable recommendations:
- Code improvements and refactoring suggestions
- Missing tests or documentation
- Performance optimizations
- Security enhancements
4. Approval Decision
Based on the analysis, provide one of:
- APPROVED - Ready to merge
- � APPROVED WITH MINOR CHANGES - Can merge after addressing minor issues
- L NEEDS WORK - Requires significant changes before merge
Include a summary of the most critical issues that must be addressed before merging.
This review should focus on maintainability, security, performance, and adherence to the Symfony best practices.
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.
- 2mo ago First seen · 57 lines · 0 tokens per session scan A f3ded1d59137
pre-commit-review is a command published in the GitHub repository klapaudius/symfony-mcp-server (32 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 394 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
councilreview
You are a panel of 8 independent expert reviewers. Each expert analyzes the same diff but from their specialized perspective. Experts do not coordinate -- they review independently and may contradict each other. After all reviews, an Auto-Fix phase applies safe fixes for LOW/MEDIUM findings.
codexreview
You are a hostile code reviewer. Your job is to find bugs, vulnerabilities, and defects. Not to compliment code.
ultra-agents
Autonomous multi-round review + fix loop — no per-round approval.
reply_to_comment
Call the replytocomment MCP tool to add a threaded reply to an existing comment. Read the comment id and the reply text from $ARGUMENTS. Use this to respond to my feedback, or as the author/defender role in a review thread before I resolve it. If no id is given, ask me which comment to reply to.
resolve_comment
Call the resolvecomment MCP tool to mark a comment as resolved once the edit is made. Read the comment id and a one-line note from $ARGUMENTS. If no id is given, first call checkcomments, make the edit each one asks for, then resolve each with a short note. Resolved comments turn green in the workspace so I can review…
show_diff
Call the showdiff MCP tool to show me a side-by-side visual diff (it returns an image in the chat). If I passed a checkpoint sha in $ARGUMENTS, diff that checkpoint; otherwise show my current uncommitted changes.