pr-automation_skill

Overview

This skill automates pull request workflows to make PR creation fast, consistent, and reliable. It prepares rich PR descriptions, validates requirements (tests, docs, linting), flags missing items, and links related issues automatically. Use it to reduce manual overhead and improve review readiness before pushing code.

How this skill works

The skill analyzes the git diff and recent commit messages to understand what changed and why. It generates a structured PR description using a project template, runs validation checks (tests, lint, formatting, secrets), identifies missing tests or docs, and searches commit text and code context to link related issues. It can also suggest reviewers and add labels when creating the PR.

When to use it

• Before creating a pull request or when requesting PR creation
• After finishing a feature, bugfix, or refactor and before pushing
• When you want to ensure tests, docs, and formatting are present
• When you want automated issue linking and reviewer suggestions
• As a pre-push or CI step to catch missing requirements early

Best practices

• Run the skill locally or via the pre-push hook before opening a PR
• Keep commit messages clear and reference issues to improve auto-linking
• Keep CODEOWNERS and team metadata updated to improve reviewer suggestions
• Address validation failures (tests, lint, formatting) before creating the PR
• Review the generated PR description and testing checklist for accuracy

Example use cases

• Create a PR for a new feature: auto-generate description, checklist, and link the feature issue
• Submit a hotfix: verify tests pass, ensure no secrets were committed, and add proper labels
• Refactor code: detect missing API docs and suggest reviewers familiar with the module
• CI pre-merge step: run validation to prevent merges that break tests or style rules
• Onboarding contributors: provide consistent PR templates and automated checks to guide quality