What is git-branch-commit-pr?

A workflow tool for Lua code changes that creates a feature branch, makes the requested edits, reviews them, commits the result, and opens a pull request. A pull request is a proposed change for review before merging it into a shared codebase.

Use it for Lua improvements or fixes that need a branch, repository validation, a commit, and a pull request.

It keeps branch, validation, documentation, and review steps together instead of leaving them to memory. It also checks related files when a Lua change affects public behavior.

git-branch-commit-pr — Skill for Claude Code and Codex by juhaku: A workflow tool for Lua code changes that creates…

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add skills/juhaku/aiwaku.nvim/git-branch-commit-pr

Any agent

npx skills add juhaku/aiwaku.nvim --skill git-branch-commit-pr

Clone the repo

git clone --depth 1 https://github.com/juhaku/aiwaku.nvim

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/juhaku/aiwaku.nvim/git-branch-commit-pr.svg)](https://agentmods.dev/skills/juhaku/aiwaku.nvim/git-branch-commit-pr)

Your own site

<a href="https://agentmods.dev/skills/juhaku/aiwaku.nvim/git-branch-commit-pr"><img src="https://agentmods.dev/badge/skills/juhaku/aiwaku.nvim/git-branch-commit-pr.svg" alt="Measured on agentmods" height="20"></a>

Per session 51 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 558 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5	$0.00051	$0.00558
Opus 5	$0.00026	$0.00279
Sonnet 5	$0.00010	$0.00112
Haiku 4.5	$0.00005	$0.00056

Measured 3d ago against content hash cb2ef6f4a895, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

git-branch-commit-pr scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.github/skills/git-branch-commit-pr/SKILL.md · 46 lines

How it starts

The opening of the file, as written. The whole thing — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Lua Code Change Workflow Skill

When tasked with creating a branch, committing code changes, and opening a pull request for this repository, follow this workflow:

Workflow Steps

Create Feature Branch
- Create a new branch with a descriptive name based on the task.
- Use the format: feature/{description}, fix/{description}, or chore/{description} as appropriate.
Make Code Changes
- Make precise, task-focused changes only.
- For Lua files, follow .github/instructions/lua.instructions.md.
- Do not limit updates to .lua files when the task also requires related documentation or configuration changes.
- Keep user-facing behavior and documentation in sync. In this repository, changes to public options, keymaps, or API behavior may also require updates to README.md and doc/aiwaku.nvim.txt.
Review Code Changes
- Validate that the code actually works before committing.
- Run the repository's existing validation steps when they exist. If there is no dedicated test or lint command, perform the most relevant available verification and state what you checked.
- Run a review pass before finalizing changes and address any substantive issues found.
Commit Changes
- Before creating the commit, confirm the intended commit message format with the user if it has not already been specified.
- Use a conventional commit message in the format type(scope): description.
- Keep the commit focused to one logical change.
- Include the required trailer:
  - Co-authored-by: Copilot <[email protected]>
Open Pull Request
- Do not push changes or open a pull request automatically without first confirming the PR title/description format with the user if it has not already been specified.
- Use the GitHub MCP server or GitHub CLI to open the pull request after confirmation.lua
- Include a meaningful title and a clearly structured description that explains what changed and why.
- Link related issues when applicable.

Read the full file on GitHub · 46 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

3d ago First seen · 46 lines · 51 tokens per session scan A cb2ef6f4a895

Subscribe to this mod's changes

git-branch-commit-pr is a skill published in the GitHub repository juhaku/aiwaku.nvim (11 stars, last pushed 2mo ago), licensed MIT. It adds 51 tokens to every session and 558 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-02.

Code review Commits Git and workflow ai cli neovim neovim-plugin

agentic-lua-class

MANDATORY before writing or editing ANY .lua file in this repo - classes, methods, fields, functions, or LuaCATS annotations. Holds the project's enforced Lua style: class pattern, visibility prefixes (private, protected), and optional-type syntax. Skipping it produces luals/selene failures at make validate. Load it…

carlos-algms/agentic.nvim · 82 tokens

agentic-ui-message-writer

MANDATORY before editing MessageWriter, PermissionManager, tool-call block rendering, sender headers, thinking blocks, auto-scroll, folds, status rows, permission buttons, or chat-buffer tool-call tests.

carlos-algms/agentic.nvim · 46 tokens

agentic-github-discussion

Use when creating, listing, or managing GitHub discussions in carlos-algms/agentic.nvim repository.

carlos-algms/agentic.nvim · 29 tokens

agentic-testing

MANDATORY before creating, editing, or reviewing tests in agentic.nvim, and before behavior changes that require TDD. Covers mini.test workflow, red/green rules, commands, mark-count checks, and which test references to load.

carlos-algms/agentic.nvim · 51 tokens

agentic-acp-protocol-flow

MANDATORY before editing ACPClient, ACPTransport, AgentInstance, ACP provider flow, tool-call parsing, permission requests, provider switch, reconnect, or ACP subprocess lifecycle in agentic.nvim.