Cursor rule Cursor
A rule for defining tools in the MCP server is clearly and effectively defined. Ensures each tool includes a well-structured title and description that communicates its purpose, functionality, ideal usage scenarios, and expected output. This improves tool discoverability, relevance ranking, and clarity for AI agents.
Command
Cleanup current branch and switch to default branch with latest changes.
Command
Commit changes and create a PR with proper formatting.
Command
Fetch all PR comments, classify by severity, and present for user approval before acting.
Command
Analyze my Cursor base context and suggest optimizations.
Command
Review only changed files in this branch Your primary goal is to provide valuable, trustworthy feedback while avoiding false positives and low-impact commentary.
Cursor rule
Require technical design docs in docs/ and feature README files next to their code.
Cursor rule
Structured approach for complex feature implementation with mandatory planning and user approval.
Cursor rule
Git Safety Rule - Require explicit permission for all git operations.
Cursor rule
When adding or editing an MCP Server's tool, follow this structure to make it clear when and how the tool should be used.
Cursor rule
Code review rule for PR analysis. Challenges architectural decisions, examines the diff with the default branch, and provides comprehensive feedback on code quality, security, performance, and maintainability before publishing.
Skill Claude CodeCodex
Stress-test a plan or design against domain language, docs, and code. Ask hard questions one at a time. Update CONTEXT.md and ADRs as decisions crystallize. Use when you already have a draft plan or spec and want to find gaps before implementation.