commit-pr

Enforce invariant audits and validation suites for commit and pull request operations.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of non-compliant commits and pull requests that fail CI gates, miss required invariant audits, or lack proper documentation, reducing merge failures and production regressions for engineering teams.

Core Features & Use Cases

  • Mandatory Invariant Audit: Enforces evidence-based checks for all 12 engineering invariants before any code changes are pushed, with clear requirements for touched invariants.
  • Gated Validation Suite: Runs tiered quality, unit, integration, security, and smoke tests, with explicit handling for pre-existing failures and generated output exclusions.
  • End-to-End PR Lifecycle Management: Automates semantic commit/PR formatting, release note fragment creation, issue commenting, conflict resolution, merge queue handling, and PR monitoring subscription.
  • Use Case: For teams using opencode-swarm, this Skill ensures every code change passes all required quality, security, and architectural invariant gates before merging, eliminating broken PRs and unplanned release regressions.

Quick Start

Use the commit-pr skill to prepare a fully compliant pull request for your latest code changes, including all required invariant audit evidence and validation results.

Frequently Asked Questions about commit-pr

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

FAQPage Schema
How do I enforce semantic commit formatting and invariant audits before creating a pull request?

To enforce semantic commit formatting and invariant audits before creating a pull request, use an automated workflow that checks all 12 engineering invariants and runs gated validation suites for quality, security, and architectural compliance.

How do I automate release note generation and semantic commit formatting for CI validation?

Automate release note generation and semantic commit formatting by integrating a PR lifecycle workflow that creates release note fragments and applies semantic formatting rules during gated CI validation checks.

What is the best way to resolve CI failures and manage merge queues for compliant pull requests?

The best way to resolve CI failures and manage merge queues is to implement end-to-end PR lifecycle management that handles conflict resolution, merge queue processing, and continuous PR monitoring.

How do I document invariant audit evidence for engineering workflows involving code commits?

Document invariant audit evidence by enforcing evidence-based checks that explicitly record which of the 12 engineering invariants were touched, ensuring full traceability before code changes are pushed.

Can I run gated quality and security checks on pre-existing CI failures without blocking new pull requests?

Yes, gated validation suites can run tiered quality and security checks with explicit handling for pre-existing failures and generated output exclusions, preventing legacy issues from blocking new pull requests.

Why do my pull requests fail CI gates and miss required invariant audits?

Pull requests fail CI gates and miss invariant audits when they lack an automated compliance workflow enforcing mandatory evidence documentation, tiered security testing, and semantic commit formatting before publication.