pr-automation

Automate pull request workflows to streamline PR creation and validation.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "pr-automation" with this command: npx skills add basedhardware/omi/basedhardware-omi-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.)

  1. 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

  1. 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

  1. 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

  1. 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

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Automation

docs-automation

No summary provided by upstream source.

Repository SourceNeeds Review
Automation

agent-modes

No summary provided by upstream source.

Repository SourceNeeds Review
Automation

browser-automation

No summary provided by upstream source.

Repository SourceNeeds Review
Automation

agent-review

No summary provided by upstream source.

Repository SourceNeeds Review