commit-pr

Enforce conventional commit formats and PR-quality gates across development workflows.

437|45|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/zaxbysauce/opencode-swarm --skill commit-pr-zaxbysauce
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-pr
Source: https://github.com/zaxbysauce/opencode-swarm/tree/main/.claude/skills/commit-pr
Command: npx skills add https://github.com/zaxbysauce/opencode-swarm --skill commit-pr-zaxbysauce

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Apply when committing, pushing, opening a PR, writing a pull request, creating release notes, or updating a changelog. Enforces conventional commit format, mandatory release notes, 5-tier test suite, SHA-pinning for workflow changes, and correct PR body format.

Core Features & Use Cases

  • Enforces conventional commit format for all messages
  • Mandates release notes and structured PR bodies
  • Includes a 5-tier test suite and SHA-pinning to stabilize workflows
  • Supports automated release notes generation and changelog updates

Quick Start

Enable this skill in your workflow and begin enforcing conventional commits, mandatory release notes, and gated PR checks for every PR.

Frequently Asked Questions about commit-pr

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

FAQPage Schema
How do I enforce conventional commits across my development lifecycle?

To enforce conventional commits, this Skill gates commit messages, pushes, and PRs to standardize authoring workflows. It mandates correct conventional formatting, structured PR bodies, and release notes for every contribution.

How do I standardize pull request bodies and release notes generation?

Standardizing pull request bodies and release notes requires mandatory structured formats. This Skill automates release notes generation and changelog updates by enforcing correct PR body formatting and requiring release notes for every approved PR.

What's the best way to gate CI-CD workflows with SHA-pinning and test suites?

Gating CI-CD workflows requires stabilizing workflow changes via SHA-pinning and verifying code quality. This Skill enforces a 5-tier test suite and SHA-pinning for workflow modifications to stabilize your automated pipelines.

Does this Skill require any dependencies to apply PR-quality gates?

No dependencies are required to apply PR-quality gates. You can enable this Skill directly in your workflow to begin enforcing gated PR checks, conventional commit formatting, and mandatory release notes without installing external components.

Why are my pull requests failing quality checks without structured release notes?

Pull requests fail quality checks without structured release notes because this Skill mandates structured PR bodies and release notes before approval. It enforces these gates to standardize authoring workflows and ensure consistent changelog updates.

When do I need to use conventional commit formatting and gated PR checks?

You need conventional commit formatting and gated PR checks when committing, pushing, opening a PR, or updating a changelog. This ensures standardized authoring, mandatory release notes, and consistent approval workflows across your development lifecycle.