A set of rules for managing work in Git, a system for tracking code changes, and GitHub, a service for hosting repositories and reviewing changes. It covers branches, commits, pull requests, issues, worktrees, releases, and changelogs.

Use it when creating or reviewing branches, commits, pull requests, issues, releases, worktrees, or other Git-related changes.

It provides consistent decisions about where changes belong and how to preserve local work. It also helps keep branch names, issue titles, commits, and pull requests organized.

git — Skill for Claude Code by mifunedev/openharness

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo

git clone --depth 1 https://github.com/mifunedev/openharness

agentmods

npx agentmods add skills/mifunedev/openharness/git

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/mifunedev/openharness/git/github.svg)](https://agentmods.dev/skills/mifunedev/openharness/git)

Your own site

<a href="https://agentmods.dev/skills/mifunedev/openharness/git"><img src="https://agentmods.dev/badge/skills/mifunedev/openharness/git/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/mifunedev/openharness/git"><img src="https://agentmods.dev/badge/skills/mifunedev/openharness/git.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

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

Security scan C 1 finding. A grade says what 26 rules found in the file — not that it is safe.

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.1	$0.00092	$0.03892
Opus 5.5	$0.00037	$0.01557
Sonnet 5.5	$0.00018	$0.00778
Haiku 4.5	$0.00009	$0.00389

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

Security

Grade C, and why

git scanned grade C 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

Worktrees older than 30 days without a corresponding open PR may be removed via `git worktree remove`; corrupted worktree directories may be removed with `rm -rf` after confirming they are not valid `git worktree list` e

.oh/skills/git/SKILL.md · 309 lines

How it starts

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

Git Workflow

Always Load This Skill

Any time a chat mentions git, GitHub, branches, commits, pushes, pulls, PRs, issues, worktrees, merge conflicts, releases, changelog entries, or dirty workspace cleanup, read this skill before acting. Treat it as the source of truth for routing changes to the right remote and for preserving local work safely.

Repository and Memory Routing

This checkout commonly has two remotes:

upstream → mifunedev/openharness (public template/canonical upstream)
origin → your fork of openharness (private/operator fork)

Before every commit or PR, inspect the changed paths and choose the remote explicitly. Do not assume origin is the public target.

Issue Titles

Format: <prefix>(<issue#>): <shortdesc>

<prefix> ∈ feat · bug · task · audit · skill · agent (matches .github/ISSUE_TEMPLATE/<prefix>.md)

Example: feat(#42): slack thread replies

Create issue first so <issue#> exists, then branch.

Branch Names

Format: <prefix>/<issue#>-<short-desc>

<short-desc>: kebab-case, ≤5 words
Base off default target branch (see below)

Example: feat/42-slack-thread-replies

Default Target Branch

Use first existing in repo:

development (preferred)
main (fallback)
master (fallback)

Detect via git show-ref --verify --quiet refs/heads/<name> (or remote refs/remotes/origin/<name>). PRs target this branch; new branches cut from it.

Git Authentication

Inside sandbox, run gh auth login && gh auth setup-git during onboarding. GitHub CLI installs credential helper — git push / git fetch use your GitHub token — no SSH keys required.

PR Titles

Format: FROM <source-branch> TO <target-branch> (literal)

Example: FROM feat/42-slack-thread-replies TO development

PR Bodies

Link issue: Closes #<issue#> (or Fixes/Resolves) in the PR title or body
Target default target branch (development → main → master, whichever exists)

Closes #N closes the issue on merge into development — the workflow does it, not GitHub. GitHub honors a closing trailer only on merge into the default branch. PRs here target development while the default branch is main, so GitHub records the trailer as a referenced timeline event and nothing else. Verified on #759 (whose closed event carries commit=none) and independently on #753 from PR #757. .github/workflows/close-issues-on-development.yml closes the gap: on a merged PR into development it parses the title and body for the nine closing keywords and closes each referenced issue as completed (#841).

The trailer is therefore load-bearing — write it on every PR. Close by hand only when the automation cannot see the merge (a direct push, a merge into another branch, a PR whose body carried no trailer, or a PR opened from a fork, which gets a read-only token):
gh issue close <N> --repo <owner/name> --comment "Merged in #<PR>."

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

1mo ago Changed · +17 lines f2f0730d931a
1mo ago First seen · 292 lines · 92 tokens per session scan C fac4f5f7d9cd

Subscribe to this mod's changes

git is a skill published in the GitHub repository mifunedev/openharness (37 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 92 tokens to every session and 3,892 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Claude Code Commits Git and workflow LangChain NVIDIA Releases codex deepagents docker

safety

Check secret handling, staged changes and push targets, destructive Git operations, Docker image hygiene, and new dependencies before consequential coding actions. Use for commits, pushes, container builds or publishes, dependency additions, and explicit safety reviews.

langchain-ai/deepagents · 48 tokens

git-ops

Close out a local coding task on the bound daemon — stage, commit, branch, merge, push via cloud git — and when a merge conflicts, STOP and escalate with the file list instead of auto-resolving. Push reaches only the bare replica; prod-triggering tags are refused.

Prismer-AI/PrismerCloud · 62 tokens

chinese-commit-conventions

A Chinese-language reference for writing commit messages and changelogs, which record code changes and releases.

xbsheng/atguigu-note · 65 tokens

conventional-git

Conventional Commits v1.0.0 branch naming and commit message standards for GitHub and GitLab projects. Use when creating branches, writing commits, generating commit messages, reviewing branch conventions, or setting up changelog automation. Apply when your project needs consistent git history, SemVer-driven releases…

Harmeet10000/skills · 77 tokens

octocat

Handles git and GitHub operations using the gh CLI. Use when the user asks about pull requests (PRs), GitHub issues, repo management, branching, merging, rebasing, cherry-picking, merge conflict resolution, commit history cleanup, pre-commit hook debugging, GitHub Actions workflows, or releases. Covers creating and…

Harmeet10000/skills · 100 tokens

git-workflow

Branch naming, commit message format, and PR conventions. Use when making git commits or creating PRs.

coltonkirsten/nexus · 25 tokens

git