commit-code

Commits staged and unstaged changes and optionally opens a GitHub PR or GitLab MR.

Updated Apr 28, 2026

Search Tags:#git #pull request #commit #github #jira #gitlab #merge request

One-click install

npx skills add https://github.com/byron1st/personal-harness --skill commit-code-byron1st

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: commit-code
Source: https://github.com/byron1st/personal-harness/tree/main/skills/commit-code
Command: npx skills add https://github.com/byron1st/personal-harness --skill commit-code-byron1st

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? It standardizes how code changes get committed and merged, enforcing consistent commit message formats, correct committer identity per repository type, and PR/MR creation only when explicitly requested. ## Core Features & Use Cases - Conventional commits with Jira integration: Generates titles like `feat: [PROJ-123] add login flow`, extracting the Jira ticket from the branch name for work repositories. - Work vs. personal repository handling: Uses the correct git identity (`$WORK_GIT_EMAIL` vs `$PERSONAL_GIT_EMAIL`) and routes PR creation to `gh pr create` (personal) or `glab mr create`/`glab mr update` (work). - Documentation drift check: After committing, compares the diff against `AGENTS.md`, `README.md`, and `docs/` and reports stale documentation without modifying anything. - Use Case: After finishing a feature on a work branch, ask to commit and open an MR — the skill commits with the Jira-prefixed title, pushes, and creates or updates the GitLab MR with reviewers assigned. ## Quick Start Ask the assistant to commit the current changes, optionally adding that it should also open a PR or MR.

Frequently Asked Questions about commit-code

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

FAQPage Schema

How do I commit changes and open a pull request in one step?▼

Ask to commit and explicitly request a PR or MR, for example by saying commit and open a PR. The skill commits the dirty tree first, then pushes and runs gh pr create for personal repos or glab mr create for work repos.

How do I create a GitLab merge request from the command line?▼

Use glab mr create with flags for assignee, reviewers, title, description, push, and remove-source-branch. If the MR already exists, glab mr update modifies the title and description instead.

Does the skill open a PR automatically after committing?▼

No. A PR or MR is opened only when the invocation explicitly asks for one, such as request-merge or open a PR. A plain commit request never triggers PR creation, even if the branch is ahead of main.

How are Jira tickets added to commit messages?▼

For work repositories, the ticket is extracted from the branch name using the pattern [A-Z]+-[0-9]+ and inserted into the title as PREFIX: [TICKET] title. If no ticket can be extracted, the skill asks the user to provide it.

What is the documentation drift check after a commit?▼

It is a read-only review comparing the committed diff against AGENTS.md, README.md, and affected docs. It reports whether docs need updates or need manual review, but never modifies, stages, or amends any files.