An independent second reader for both documents and code - reviews specs, designs, contracts and tickets for gaps and contradictions before they are handed on, and every developer diff for correctness, simplicity and fit to its ticket before it goes to QA. Writes findings and never changes what it reviews, and suggests adding agents to the team when the project or its requirements have grown past the team setup chose. Use on every spec, design and diff before the next hand-off.
Full GitLab development loop — from issue to confirmed-resolved. Covers write-issue, analyze-issue, fix-issue, review-code, create-mr, summarize-issue, triage-issue, and post-merge verification.
Use when reviewing code for security vulnerabilities, performing a security audit, or checking for OWASP Top 10 issues — covers injection flaws, broken access control, cryptographic failures, secrets exposure, dependency vulnerabilities, and language-specific pitfalls for Python, TypeScript/JavaScript, and Go.
Whole-codebase code auditor for Flutter/Dart mobile games (iOS + Android). Use to audit the ENTIRE project (not just a diff) for correctness, architecture conformance, consistency, dead code, and test coverage. Complements code-reviewer (which reviews a single diff/PR). Read-only — reports findings.
Gameplay programmer for Flutter/Dart mobile games (iOS + Android). Use to implement game systems, player abilities, interaction/collision logic, input/gesture handling, and UI flow in Dart/Flutter/Flame. Call after engine-architect; runs dart analyze/test; hands off to qa-tester and code-reviewer.
Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.
9 projects use a version of this
217k7mo agoReviewMountCreate a free account to mount
Code review focused exclusively on over-engineering. Finds what to delete: reinvented standard library, unneeded dependencies, speculative abstractions, dead flexibility. One line per finding: location, what to cut, what replaces it. Use when the user says "review for over-engineering", "what can we delete", "is this over-engineered", "simplify review", or invokes /ponytail-review. Complements correctness-focused review, this one only hunts complexity.
Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.
Steady5 mentions in 2 weeks
No other project uses it yet
2.9k2mo agoReviewMountCreate a free account to mount
This rule governs the process of committing and pushing changes to git repositories. It should be applied whenever: (1) The user indicates they want to commit or push changes, (2) The user asks about git commit conventions, (3) The user wants to update or save their work to git, or (4) Any git-related commit and push operations are requested. The rule ensures consistent commit message formatting, proper change documentation, and maintainable git history. It's particularly important for maintaining clear project history, facilitating code reviews, and ensuring proper documentation of changes. This rule helps maintain high-quality commit messages that explain both what changed and why, making it easier for both humans and AI to understand the project's evolution.
119mo agoReviewMountCreate a free account to mount
Capability-security review of PRs, diffs, or third-party/plugin code — apply when reviewing pull requests, auditing contributed code, or judging whether code is safe.
Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.
346mo agoReviewMountCreate a free account to mount
Blueprint — behavioral guidelines for coding agents. Use when writing, reviewing, or refactoring code to ensure accuracy, simplicity, and surgical changes.
Self-review checklist for the coding agent to run before dispatching a reviewer. Checks CONVENTIONS.md compliance, Boy Scout Rule, test coverage, types, and SOLID. Produces a pass/fail checklist. Use before request-review, before committing, or when user asks for a code quality check.
2867d agoReviewMountCreate a free account to mount
Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.
Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.
Use when writing or reviewing Python code — naming conventions, type hints, common pitfalls (mutable defaults, bare except, is-vs-==), and testing structure.
Fadi88Cursor rule
