llamafarm: Skill for Claude Code

.claude/skills/commit-push-pr/SKILL.md

commit-push-pr is a skill for Claude Code from llama-farm/llamafarm. It costs 36 tokens per session (2,340 once invoked), scanned A, original, Apache-2.0.

A Git workflow helper that commits local changes, pushes the branch to GitHub, and opens a pull request for review. It also runs listed quality checks unless quick mode is used.

In plain words
What is it for?
Use it to turn finished code changes into a reviewed GitHub pull request, while following commit and pre-commit-hook rules.
Why use it?
It removes the need to repeat the same Git commands and helps check changes before asking others to review them.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the AskUserQuestion tool.

This is llama-farm/llamafarm's own configuration. It tells Claude Code how to work on llamafarm itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything llamafarm configures →

Reuse

Borrowing it

Nothing to install: this file belongs to llama-farm/llamafarm. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/llama-farm/llamafarm/main/.claude/skills/commit-push-pr/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/llama-farm/llamafarm

Made for: Claude Code.

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.

agentmods badge for commit-push-pr

README.md
[![agentmods](https://agentmods.dev/badge/skills/llama-farm/llamafarm/commit-push-pr/github.svg)](https://agentmods.dev/skills/llama-farm/llamafarm/commit-push-pr)
Your own site
<a href="https://agentmods.dev/skills/llama-farm/llamafarm/commit-push-pr"><img src="https://agentmods.dev/badge/skills/llama-farm/llamafarm/commit-push-pr/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for commit-push-pr

Your own site · 80×15
<a href="https://agentmods.dev/skills/llama-farm/llamafarm/commit-push-pr"><img src="https://agentmods.dev/badge/skills/llama-farm/llamafarm/commit-push-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 36 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,340 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00036 $0.02340
Opus 5.5 $0.00014 $0.00936
Sonnet 5.5 $0.00007 $0.00468
Haiku 4.5 $0.00004 $0.00234

Measured 1mo ago against content hash afc4fb6d1a3a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

commit-push-pr scanned grade A with 1 finding 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 1mo 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.

Runs shell commandslowCapability

Expected in a hook, worth knowing in a rule or an instructions file.

| Command injection (`shell=True`, `os.system`) | BLOCK | Cannot auto-fix - user must refactor |
.claude/skills/commit-push-pr/SKILL.md · 337 lines

How it starts

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

Commit, Push & PR Skill

Automates the git workflow of committing changes, pushing to GitHub, and opening a PR with intelligent handling of edge cases.

Required Reading

Before executing, internalize the git workflow standards: @.claude/rules/git_workflow.md

Key rules:

  • Use Conventional Commits format: type(scope): description
  • NEVER attribute Claude in commits or PRs (no co-author, no mentions)
  • NEVER skip pre-commit hooks (no --no-verify)

Execution Workflow

Step 1: Assess Git State

Run these commands to understand the current state:

# Detect the default branch (main, master, etc.)
DEFAULT_BRANCH=$(git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's@^refs/remotes/origin/@@')
# Fallback if symbolic-ref fails (e.g., shallow clone or missing HEAD)
if [ -z "$DEFAULT_BRANCH" ]; then
  DEFAULT_BRANCH=$(git remote show origin 2>/dev/null | grep 'HEAD branch' | awk '{print $NF}')
fi
# Final fallback to 'main' if detection fails
DEFAULT_BRANCH=${DEFAULT_BRANCH:-main}

# Get current branch
BRANCH=$(git branch --show-current)

# Check for uncommitted changes
git status --porcelain

# Check for unpushed commits (if branch has upstream)
git log origin/$DEFAULT_BRANCH..HEAD --oneline 2>/dev/null || echo "No upstream or no commits ahead"

# Check if branch has upstream tracking
git rev-parse --abbrev-ref @{upstream} 2>/dev/null || echo "No upstream"

Determine the state:

  • HAS_CHANGES: Are there uncommitted changes (staged, unstaged, or untracked)?
  • HAS_UNPUSHED: Are there commits ahead of origin/$DEFAULT_BRANCH?
  • ON_DEFAULT_BRANCH: Is current branch the default branch ($DEFAULT_BRANCH)?
  • HAS_UPSTREAM: Does the branch track a remote?

Step 2: Handle "Nothing to Do" Case

If !HAS_CHANGES && !HAS_UNPUSHED:

Inform user: "No changes to commit and no unpushed commits. Nothing to do."
Exit gracefully.

Step 3: Handle "No Changes But Unpushed Commits" Case

If !HAS_CHANGES && HAS_UNPUSHED:

  1. Check if PR already exists:
gh pr list --head "$(git branch --show-current)" --json number,url,title

Read the full file on GitHub · 337 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.

  1. 1mo ago First seen · 337 lines · 36 tokens per session scan A afc4fb6d1a3a

Subscribe to this mod's changes

commit-push-pr is a skill published in the GitHub repository llama-farm/llamafarm (836 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 36 tokens to every session and 2,340 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

pr

Draft a PR body from OMC's paper trail — the smallest visual that proves the change, evidence consumed from the verify protocol (never re-collected), reversibility from the ADR test on the diff, glossary language throughout.

Yeachan-Heo/oh-my-claudecode · 47 tokens

otto-pr-review-loop

Run Polly and OCR on a PR until all findings settle.

omnigent-ai/omnigent · 17 tokens

engram-branch-pr

PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.

Gentleman-Programming/engram · 37 tokens

github-contributor

A step-by-step guide for contributing code, tests, documentation, or build changes to open-source projects you do not maintain. It explains how to prepare a pull request that follows the project’s rules and is easier for maintainers to review.

daymade/claude-code-skills · 105 tokens

revdiff

Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in agterm/tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos…

umputun/revdiff · 248 tokens

re0-merge

Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…

LilMGenius/paperthin · 70 tokens