commit-pr

Name: commit-pr
Availability: InStock
Author: trader-rm

Enforce conventional commit formatting, release notes, and PR body structure.

Updated Aug 23, 2026

Search Tags:#workflow #linting #commit #pull-request #release-notes #conventional-commit

Ready to run

npx skills add https://github.com/trader-RM/ultra-swarm --skill commit-pr-trader-rm

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit-pr
Source: https://github.com/trader-RM/ultra-swarm/tree/main/base/opencode-swarm/.claude/skills/commit-pr
Command: npx skills add https://github.com/trader-RM/ultra-swarm --skill commit-pr-trader-rm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforces a standardized commit and PR workflow including conventional commit formatting, mandatory release notes, a structured PR body, and SHA pinning for workflow changes to reduce merge conflicts and non-compliance.

Core Features & Use Cases

Enforce conventional commit format: <type>(<scope>): <description>
Mandate release notes and a properly structured PR body
Validate and guide a 5-tier test suite and SHA pinning for workflow changes
Apply across local commits, feature branches, PRs, and changelog updates in multi-repo projects

Quick Start

Follow the Commit & PR Protocol for every commit, PR, and release note update.

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 commit formatting across a multi-repo project?▼

To enforce conventional commit formatting across multi-repo projects, you need a protocol that validates strict formatting checks for commit messages and applies them consistently to local commits, feature branches, and pull requests.

What is the conventional commit format for pull requests and changelog updates?▼

The conventional commit format requires messages to follow the <type>(<scope>): <description> structure, ensuring standardized pull request bodies and consistent changelog updates across the software development workflow.

How do I mandate release notes and a structured PR body in my workflow?▼

To mandate release notes and a structured PR body, implement a commit and PR protocol that enforces strict formatting checks, validates the PR body structure, and requires release notes for every pull request.

Can I pin SHAs for workflow changes alongside enforcing conventional commits?▼

Yes, you can pin SHAs for workflow changes while enforcing conventional commits. The protocol validates and guides SHA pinning for workflow changes alongside enforcing commit message formats and structured PR bodies.

What's the best way to standardize commit and PR discipline to reduce merge conflicts?▼

The best way to standardize commit and PR discipline is to enforce a protocol that applies strict formatting checks to commit messages, mandates release notes, structures PR bodies, and pins SHAs for workflow changes to reduce merge conflicts.

Why do I need a structured PR body and release notes for feature branches?▼

A structured PR body and mandatory release notes are needed for feature branches to reduce non-compliance and merge conflicts. This protocol enforces strict formatting checks and validates the PR body structure across all updates.