commit

Creates git commits and drives approved changes through pull request merge to main.

96|11|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/thefrederiksen/devthrottle --skill commit-thefrederiksen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/thefrederiksen/devthrottle/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/thefrederiksen/devthrottle --skill commit-thefrederiksen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Committing work is only half the job in a trunk-based repository; this Skill enforces a complete delivery workflow that takes approved changes from a working tree all the way to a merged pull request on origin/main, so nothing is left sitting on a side branch. ## Core Features & Use Cases - Scoped Commit Planning: Gathers changes via git status, runs a code review gate, and presents a file list plus a conventional commit message (feat, fix, refactor, docs, style, test, chore) for explicit user approval. - Trunk-Based Delivery: Never commits directly on main; creates a short-lived branch or an isolated worktree on shared checkouts, pushes, opens a pull request with gh, and merges with squash once local tests pass. - Local Test Gate and Cross-Agent Review: Runs the repository's test-local script before opening the pull request and requires a review from a different agent family (default Codex) instead of waiting on slow continuous integration. - Use Case: After finishing a bug fix, invoke /commit to have the change reviewed, committed with a standards-compliant message, pushed, merged to main, and the checkout parked back on a clean main branch. ## Quick Start Ask the assistant to commit the changes from this session using the /commit workflow and approve the proposed commit plan when presented.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I commit changes following project commit standards?▼

Invoke the /commit command or ask to commit changes. The workflow runs git status, performs a code review, proposes a conventional commit message with a type prefix like feat or fix, and waits for your explicit approval before committing.

How does trunk-based development handle pull requests after committing?▼

After approval, the change is pushed on a short-lived branch, a pull request is opened with gh pr create, and it is squash-merged once local tests pass and a review from a different agent family is clean. The branch is deleted and the checkout returns to main.

Can I commit directly on the main branch?▼

No, committing directly on main is never allowed. If the checkout is on main, a feature branch is created first; on a shared checkout, an isolated git worktree off origin/main is used instead of moving the shared HEAD.

What happens if the code review fails before committing?▼

A failed review blocks the commit and shows the blocking issues. You can reply "fix issues" for help, fix manually and rerun /commit, or reply "commit anyway" to bypass after confirming you understand the risks.

Why does the workflow not wait for continuous integration checks?▼

The continuous integration build takes roughly fifty minutes, so a verdict arriving that late is never read. Instead, local tests run first as the gate, a cross-agent review covers what tests cannot, and continuous integration acts as a backstop after merge.