pr-automation
PR Automation Skill
Automate pull request workflows to streamline PR creation and validation.
When to Use
Use this skill when:
- Before creating a PR
- When user requests PR creation
- Before pushing code to remote
- After completing a feature or fix
Capabilities
1. Generate PR Descriptions
Automatically generate comprehensive PR descriptions:
- Analyze git diff to understand changes
- Extract commit messages for context
- Identify changed files and their purposes
- Generate structured PR description following template
- Include all required sections (description, changes, testing, etc.)
2. Validate PR Requirements
Check PR requirements before creation:
- Verify tests exist for new features
- Check that tests pass
- Verify documentation is updated
- Validate code follows project conventions
- Check for linting errors
- Verify formatting is correct
- Ensure no secrets or credentials are committed
3. Check for Missing Tests/Docs
Identify missing requirements:
- Check if new features have tests
- Verify documentation is updated
- Check for missing type hints (Python)
- Verify error handling is documented
- Check for missing API documentation
4. Link Issues Automatically
Automatically link related issues:
- Parse commit messages for issue references (#123)
- Search for related issues based on changes
- Add "Closes #123" or "Related to #123" to PR description
- Link to parent issues or epics
5. Suggest Reviewers
Suggest appropriate reviewers:
- Based on files changed (domain expertise)
- Based on previous reviewers of similar changes
- Based on code owners (if CODEOWNERS file exists)
- Based on team structure
Workflow
- Analyze Changes: Review git diff and commit history
- Generate Description: Create comprehensive PR description
- Run Validation: Check all PR requirements
- Fix Issues: Address any validation failures
- Create PR: Generate PR with all information
- Post-Creation: Add labels, assign reviewers, link issues
PR Description Template
Follows the template from .cursor/rules/context-communication.mdc:
- Description of what changed and why
- Related issue links
- List of changes
- How it was verified
- Related code references
- Assumptions made
- Breaking changes (if any)
- Testing checklist
Related Resources
Rules
.cursor/rules/git-workflow.mdc- Git workflow and PR process.cursor/rules/context-communication.mdc- PR description best practices.cursor/rules/testing.mdc- Testing requirements
Subagents
.cursor/agents/pr-manager.md- PR management subagent.cursor/agents/code-reviewer.md- Code review subagent.cursor/agents/test-runner.md- Test runner subagent
Commands
/auto-pr- Generate PR with automation/pr- Create pull request with proper description/code-review- Review code before PR
More from basedhardware/omi
local-dev
Start local development environment — backend, macOS app, or Flutter mobile in iOS simulator. Use when: 'run the app', 'start backend', 'run simulator', 'flutter run', 'local dev', 'start dev environment', 'run mobile app'.
45rotate-key
Rotate an API key or secret across all locations — local .env files, macOS Keychain, GCP Secret Manager, Kubernetes deployments, and Codemagic CI. Use when: 'rotate key', 'update key', 'key leaked', 'replace secret', 'new API key', 'update GEMINI key', 'rotate secret'.
26self-improvement
Meta-skill for analyzing PRs, issues, and user interactions to improve Cursor rules and skills automatically
14debug-mode
Debug mode workflows and best practices for troubleshooting bugs, regressions, and performance issues. Use when debugging tricky issues that standard agent interactions struggle with.
13docs-automation
Automate documentation updates when API endpoints, functions, or architecture change. Detects code changes that require doc updates, generates API reference from FastAPI routers, updates architecture diagrams, and syncs between internal and external docs.
13omi-flutter-patterns
Flutter Dart BLE device communication state management Provider backend integration localization cross-platform iOS Android
13