pr

Automate GitHub pull request workflows with tests, lint, and license checks.

Updated Jan 8, 2026
One-click install
npx skills add https://github.com/invowk/invowk --skill pr-invowk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/invowk/invowk/tree/main/.claude/skills/pr
Command: npx skills add https://github.com/invowk/invowk --skill pr-invowk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GitHub pull requests often require manual coordination of tests, linting, and license checks, which can slow down delivery and introduce inconsistencies.

Core Features & Use Cases

  • Automated PR validation: run tests, lint, and license checks to ensure PRs meet quality gates.
  • Branch automation: create and switch to feature branches, aligning with conventional commit practices.
  • PR creation and description: generate informative PR bodies that reference related issues.

Quick Start

Run the PR workflow to validate changes by executing the predefined Make targets for tests, lint, and license checks.

Frequently Asked Questions about pr

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate GitHub pull request validation for tests and linting?

Automate GitHub pull request validation by executing predefined Make targets to run tests, lint, and license checks. This orchestration ensures consistent quality gates and merge readiness across individual repos or multi-repo environments without manual coordination.

Can I automate feature branch creation aligned with conventional commits?

You can automate feature branch creation and switching to align with conventional commit practices. The workflow orchestrates branch scaffolding through Makefile targets and conventions, ensuring consistent naming and structure before pushing changes or opening pull requests.

How do I generate informative PR descriptions that reference related issues?

Generate informative PR descriptions automatically by utilizing predefined PR templates. The workflow scaffolds PR bodies that clearly reference related issues, ensuring consistent documentation context when developers open pull requests on GitHub.

Does this PR workflow support multi-repo environments?

The PR workflow fully supports multi-repo environments. It orchestrates checks, branch creation, and PR templates across multiple repositories using Makefile targets and conventions to maintain consistent quality gates and merge readiness throughout the project.

What is the best way to streamline pull request workflows with automated checks?

The best way to streamline pull request workflows is to orchestrate automated checks via Makefile targets. Running tests, lint, and license validations automatically enforces quality gates consistently, reducing manual coordination and accelerating delivery.

Do I need Makefile targets to run pull request checks?

You need predefined Makefile targets to run pull request checks. The workflow orchestrates tests, lint, license validations, and branch scaffolding directly through these Makefile targets and conventions to ensure consistent merge readiness.