Repository files navigation

⭐Featured byCursor

A curated collection of Cursor slash-command prompts that give your teamreusable, version-controlled AI workflows directly inside the Cursor IDE.

🔗 Also check outCursor Hooks - that runs after every file edit

Cursor Commands are reusable AI prompts saved as Markdown files in.cursor/commands/. When you type/ in Cursor's chat input, the IDE listsevery command from your project and your global library so you can insert theprompt instantly. They act like AI-driven shortcuts that automate repetitivetasks, reinforce team standards, and keep feedback consistent.

• 🚀 Quick access: Type/ to surface every command without leaving your flow
• 🔄 Reusable: Standardize prompts for common tasks across the whole team
• 👥 Shareable: Store commands in git so they ship with your repository
• 🎯 Focused: Each command targets a specific workflow with clear structure
• 📝 Customizable: Edit or extend the Markdown files to match your processes

Commands can live in two places:

• Project commands: Store Markdown files in.cursor/commands inside your repository
• Global commands: Store personal commands in~/.cursor/commands on your machine

Cursor automatically scans both directories when you type/, combines theresults, and inserts the selected command into the chat ready to run.

1. Type/ in Cursor's AI chat or agent input
2. Select from the available commands
3. Let the AI execute the prompt with the relevant project context

• Create a.cursor/commands directory in your project root
• Add.md files with descriptive names (for example,code-review.md,run-all-tests-and-fix.md)
• Write clear Markdown instructions describing what the command should accomplish
• Open Cursor, type/, and choose your new command to execute it immediately

Example structure:

.cursor/└── commands/    ├── accessibility-audit.md    ├── add-documentation.md    ├── add-error-handling.md    ├── address-github-pr-comments.md    ├── code-review.md    ├── create-pr.md    ├── database-migration.md    ├── debug-issue.md    ├── fix-compile-errors.md    ├── fix-git-issues.md    ├── generate-api-docs.md    ├── generate-pr-description.md    ├── light-review-existing-diffs.md    ├── lint-fix.md    ├── lint-suite.md    ├── onboard-new-developer.md    ├── optimize-performance.md    ├── refactor-code.md    ├── run-all-tests-and-fix.md    ├── security-audit.md    ├── security-review.md    ├── setup-new-feature.md    └── write-unit-tests.md

• lint-fix.md – Automatically analyze and fix linting issues in the current file
• lint-suite.md – Run project linters, apply fixes, and ensure codebase meets formatting requirements
• refactor-code.md – Improve code quality while maintaining functionality
• optimize-performance.md – Analyze and optimize code performance
• add-error-handling.md – Implement comprehensive error handling across the change set

• code-review.md – Comprehensive review checklist with structured steps and focus areas
• address-github-pr-comments.md – Process reviewer feedback and craft thoughtful responses
• light-review-existing-diffs.md – Quick pass to highlight risky diffs and cleanup items
• create-pr.md – Prepare a well-structured pull request with validation checklist
• generate-pr-description.md – Draft detailed pull-request descriptions automatically

• run-all-tests-and-fix.md – Execute the full suite, triage failures, and confirm fixes
• write-unit-tests.md – Generate focused unit tests with proper coverage
• debug-issue.md – Step-by-step debugging workflow for isolating defects
• fix-compile-errors.md – Diagnose and resolve compilation failures quickly

• add-documentation.md – Capture comprehensive product or code documentation
• generate-api-docs.md – Produce rich API documentation with schemas and examples
• onboard-new-developer.md – Checklist-driven onboarding for new teammates
• setup-new-feature.md – Plan requirements, branching, and architecture for new work

• security-audit.md – Structured security checklist for code changes
• security-review.md – Broader vulnerability and risk assessment workflow
• accessibility-audit.md – Review for WCAG compliance issues
• database-migration.md – Plan, create, and validate database migrations with rollbacks
• fix-git-issues.md – Resolve merge conflicts and repository problems safely

1. Clone this repository or copy the.cursor/commands/ directory into your project
2. Open the project in Cursor IDE
3. Type/ in the AI chat to browse available commands
4. Select a command and let Cursor execute the prompt with your code context

# Option 1: clone the repositorygit clone https://github.com/hamzafer/cursor-commands.gitcd cursor-commands

# Option 2: copy commands into an existing projectcp -r cursor-commands/.cursor /path/to/your/project/

Alternatively, create the directory manually:

1. Create.cursor/commands/ in your project root
2. Copy or author the Markdown command files you need

Use the existing files as templates or start from scratch:

touch .cursor/commands/my-custom-command.md

#My Custom CommandBrief description of what this command does.##ObjectiveDetailed explanation of the task and expected outcome.##Requirements- Specific requirements or constraints- Coding standards to follow- Expected formats or structures##OutputDescription of what the AI should produce.Provide clear instructions for the AI to follow.

#Generate API DocumentationCreate comprehensive API documentation for the current code. Include:- Endpoint descriptions and HTTP methods- Request/response schemas with examples- Authentication requirements- Error codes and responses- Rate limiting informationFormat as OpenAPI/Swagger specification.

#Security AuditPerform a security audit of the current code. Check for:- SQL injection vulnerabilities- XSS attack vectors- Authentication and authorization issues- Input validation problems- Sensitive data exposureProvide specific remediation steps for each issue found.

• Be specific: Describe the expected outcome and acceptance criteria
• Provide context: Reference project conventions, architecture, or standards
• Set boundaries: Clarify scope, assumptions, and tooling limits
• Include examples: Show expected formats or responses when helpful
• Stay focused: Keep each command targeted to a single, clear objective
• Review together: Treat command changes like code changes and review in PRs
• Use descriptive names: Make filenames reflect the command's purpose

• Changelog – v1.6
• Docs – Custom Slash Commands
• Announcement Post 1
• Announcement Post 2

• Open anissue for feedback or requests
• Refer to this README for the command index that ships with the prompts

This project is open source and available under theMIT License.