skills.rest
AlexanderNarbaev
AlexanderNarbaevCOMMUNITY
Explore all skills by this author →
𝕏@alex_foullyGitHub

commit-pr

Enforces a structured commit, validation, and pull request publication protocol for GitHub repositories.

Updated May 31, 2026
Search Tags:#code review#pull request#github#release notes#commit protocol#merge queue#ci validation
One-click install
npx skills add https://github.com/AlexanderNarbaev/agi --skill commit-pr-alexandernarbaev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit-pr
Source: https://github.com/AlexanderNarbaev/agi/tree/main/.opencode/skills/commit-pr
Command: npx skills add https://github.com/AlexanderNarbaev/agi --skill commit-pr-alexandernarbaev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Publishing code changes often skips critical steps: missing invariant audits, unformatted PR titles that fail CI, forgotten release notes, unposted issue comments, and premature merge-ready claims while checks are still pending. This Skill enforces a complete, ordered commit-and-PR protocol so nothing is skipped. ## Core Features & Use Cases - Mandatory invariant audit: Requires reading AGENTS.md and engineering-invariants.md before any push, with per-invariant evidence recorded in the PR body. - Full validation tiers: Runs build, typecheck, lint, unit, integration, security, adversarial, and smoke test tiers before pushing, with pre-existing failure isolation via git worktree. - PR lifecycle management: Covers semantic PR titles, release-note fragments, publication-gate evidence files, issue comments, review follow-up, merge queue handling, and cancelled-job recovery. - Use Case: After fixing a bug, an agent runs the full validation suite, creates a release fragment, opens a semantically titled PR with an invariant audit and test plan, posts the mandatory issue comment, and only marks the PR ready once all required checks on the current head SHA are green. ## Quick Start Use the commit-pr skill to commit my changes, run the full validation suite, and open a pull request that closes the linked issue.

Frequently Asked Questions about commit-pr

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

FAQPage Schema
How do I create a pull request that passes semantic title CI checks?▼

Use the format type(scope): description exactly, with a lowercase description and no trailing period. Allowed types are feat, fix, perf, revert, docs, chore, refactor, test, ci, and build. The squash merge commit message must match the PR title.

What validation should run before pushing a branch for a PR?▼

Run the build and dist import check, typecheck, lint with the pinned Biome version, then unit, integration, security, adversarial, and smoke test tiers. Prove any unrelated failure reproduces on clean origin/main using a git worktree before documenting it as pre-existing.

Why does GitHub push protection block my commit?▼

Push protection blocks literal secret patterns like sk_live, ghp_, xox, AKIA, eyJ, and AIza even in test fixtures. Fix it by constructing fixture strings via concatenation so the forbidden pattern never appears verbatim in source.

Should I rebase my PR when main advances with a merge queue enabled?▼

No. With a merge queue, GitHub re-runs required workflows against the queued change on top of the latest main, so manual freshness rebases are unnecessary. Only rebase for genuine conflicts, stale review threads, or correctness issues against current main.

What must a PR body contain before marking it ready?▼

The body needs a Closes line when resolving an issue, plus Summary, Invariant audit, and Test plan sections. All required CI checks must be green on the current head SHA, and the issue comment with PR link, changes, usage, and migration notes must be posted.

Related Skills

Explore More Software Engineering Skills→
cursorcursor
2.6k

new-branch-and-pr

Create a feature branch from main and open a pull request.

Official
Intermediate
UlanxxUlanxx

land-and-deploy

Merge pull requests, deploy to production, and verify health via canary checks.

Community
Advanced
0xdeafcafe0xdeafcafe

drive-pr

Resolve trusted GitHub PR feedback, fix CI failures, and update descriptions.

Community
Advanced
everquinteverquint

eq-frontend-workflow

Enforces trunk-based git workflow covering branches, worktrees, commits, PRs, reviews, releases, and rollbacks.

Official
Advanced