git
Skill0 starsChanged 4 months agoMITView on GitHub
Use for git and GitHub PR operations. Owns the local-git + PR surface — branches (sprint, story, bug, revert, refactor), checkout, commit, push, and PR create/read/list/review/delete. Confirms before mutating ops.
- Commits and pushes
57 other projects use a version of this.
Adopted by
Most recently taken up by
- bmcszk/agent-skillstheir own version, first seen Nov 8, 2026
- BridgLabs/opencodereviewtheir own version, first seen Nov 8, 2026
- Conceptual-Machines/magda-coretheir own version, first seen Nov 7, 2026
- tsukhani/jclawtheir own version, first seen Nov 5, 2026
- cekrauseee/harnesstheir own version, first seen Nov 1, 2026
- jmlrt/skillstheir own version, first seen Nov 1, 2026
Used with
Projects with it also use sql, databases and 9 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
thechandanbhagatSkillsql
Write SQL queries, optimize database performance, design schemas, and debug SQL issues. Use for database operations, query optimization, and schema design.
Also in 4 projects that use this
mrgoonieSkilldatabases
Work with MongoDB (document database, BSON documents, aggregation pipelines, Atlas cloud) and PostgreSQL (relational database, SQL queries, psql CLI, pgAdmin). Use when designing database schemas, writing queries and aggregations, optimizing indexes for performance, performing database migrations, configuring replication and sharding, implementing backup and restore strategies, managing database users and permissions, analyzing query performance, or administering production databases.
Also in 3 projects that use this
mrgoonieSkilldevops
Deploy to Cloudflare (Workers, R2, D1), Docker, GCP (Cloud Run, GKE), Kubernetes (kubectl, Helm). Use for serverless, containers, CI/CD, GitOps, security audit.
Also in 4 projects that use this
MicrosoftSkilltypescript
TypeScript best practices for this monorepo. Use this skill when: (1) writing new TypeScript code, (2) reviewing TypeScript code, (3) working with API responses, fetch calls, or JSON parsing, (4) adding or modifying types and interfaces.
Also in 4 projects that use this
VercelSkillreact
React renderer for json-render that turns JSON specs into React components. Use when working with @json-render/react, building React UIs from JSON, creating component catalogs, or rendering AI-generated specs.
Also in 3 projects that use this
Microsoft AzureSkilltest
Also in 8 projects that use this
Other versions57 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 57
- macro-inc/macro★ 6ksame name
- epicenter-md/epicenter★ 4.8ksame name
- EpicenterHQ/epicenter★ 4.8ksame name
- carapace-sh/carapace-bin★ 2ksame name
- LuisaGroup/LuisaCompute★ 1.1ksame name
- kagenti/kagenti★ 303same name
- Conceptual-Machines/magda-core★ 258same name
- typv/nest-turbo-starter★ 224same name
- BridgLabs/opencodereview★ 79same name
- matteing/opal★ 59same name
47 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
- checkpointSkill
- design-themeSkill
- dispatch-agentsSkill
- githubSkill
- github-templatesSkill
- productSkill
- technical-designSkill
- user-storiesSkill
The file
We split this skill into the rules it gives an agent
12 rules. 0 are common, 5 are distinctive, and 7 are very specific to this project.
0
Common
Most of the 51 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Run Confirmation Protocol before mutating ops.
- Very specific: line 51
Before any mutating op: summarise all planned mutations in one block, ask once "Proceed?
- Very specific: line 78
Remove stop words: a, an, the, and, or, for, to, of, in, on, at, by, with, when, then.
- Distinctive: line 79
Keep first 4 remaining words.
- Very specific: line 81
Collision: if the derived name exists on remote (check via Check Branch Exists), append -2, -3, etc.
- Very specific: line 169
Never hardcode owner/repo — always derive via gh repo view from the codebase directory.
- Very specific: line 170
Never write commit message content — the caller provides {message}.
- Very specific: line 171
Never write PR or review body content from scratch — render via github-templates.
- Distinctive: line 172
Never auto-create missing base branches — stop and surface.
- Distinctive: line 173
Never run mutating ops without confirmation, even from a higher-level orchestrator.
- Very specific: line 174
Never silently swallow errors other than remote ref does not exist on delete.
- Distinctive: line 175
Never operate on a codebase whose path isn't in the Codebases table.
“Common” is measured: kept by at least 6 in 10 of the 51 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Git and PR Operations
Prerequisites: gh CLI installed + authenticated. gh: command not found or auth error → stop and surface, no workarounds.
- Resolve repo per Repo Derivation — codebases resolve independently.
- Run Confirmation Protocol before mutating ops.
- Multi-codebase ops → per codebase → aggregate into one report.
Operation Index
| Request shape | Section |
| Create branch (any kind) | Create Branch |
| Checkout / switch / go to branch | Checkout |
| Branch exists check | Check Branch Exists |
| Commit and push | Commit and Push |
| Delete branch / clean up | Delete Branch |
| Delete all story branches | Delete All Story Branches |
| Create / open / raise PR | Create PR |
| Show / view / read PR | Fetch PR |
| List PRs | List PRs |
| Approve / LGTM / request changes / review | Submit Review |
| Merge / squash / land PR | Merge PR |
| Diff / compare branches | Diff Branch Files |
Placeholders
{N}— issue number (#42→42). Infeature/sprint-{N}, the sprint number.{short-description}— derived per Branch Naming.{branch}/{branch_name}— full branch name from the caller or context.{message}— commit message, provided by the caller.{files}— file paths to stage, provided by the caller.{body}— PR or review body, rendered via thegithub-templatesskill.
Repo Derivation
owner/repo derived at runtime, never hardcoded. Run from inside the codebase directory (path from the Codebases table, never cwd); derive once per codebase and cache.
gh repo view --json owner,name --jq '[.owner.login,.name]|join("/")'Confirmation Protocol
Before any mutating op: summarise all planned mutations in one block, ask once "Proceed? (y/n)", proceed only if confirmed.
| Class | Confirmation |
| Read-only (list, fetch, check exists, diff) | Skip |
| Create branch, checkout, commit, push, create PR, submit review | Standard |
| Delete branch, delete all story branches, force push | Always, even within a larger flow |
Branch Naming
| Context | Pattern | Base branch |
| Sprint | feature/sprint-{N} | main |
| Story | feature/issue-{N}-{short-description} | feature/sprint-{N} |
| Bug (production) | fix/issue-{N}-{short-description} | main |
| Bug (in-sprint) | fix/issue-{N}-{short-description} | feature/sprint-{N} |
| Revert | revert/issue-{N}-{short-description} | main |
| Refactor (standalone) | refactor/issue-{N}-{short-description} | main |
| Refactor (in-sprint) | refactor/issue-{N}-{short-description} | feature/sprint-{N} |
| Design system (setup) | chore/design-system | codebase default branch |
Base fixed by caller, never inferred — caller names which Branch Naming row applies. Standalone bug/refactor → base off main; in-sprint bug/refactor → base off sprint branch.
short-description derivation:
- Strip leading
[Tag]prefix (e.g.[Story],[Bug]). - Lowercase; replace spaces and special chars with hyphens.
- Remove stop words:
a,an,the,and,or,for,to,of,in,on,at,by,with,when,then. - Keep first 4 remaining words; trim trailing hyphens.
Collision: if the derived name exists on remote (check via Check Branch Exists), append -2, -3, etc. until unique.
Operations
Create Branch
git checkout {base_branch} && git pull
git checkout -b {new_branch}
git push -u origin {new_branch}Story branches: confirm the sprint branch exists via Check Branch Exists first; absent → stop and surface, never auto-create. Run the collision check before creating.
Checkout
git checkout {branch_name}
git pull"Checkout sprint branch" → feature/sprint-{N} for the current sprint.
Check Branch Exists
git ls-remote --exit-code --heads origin {branch_name} — exit 0 = exists (true), exit 2 = not found (false).
Commit and Push
git add {files}
git commit -m "{message}"
git push origin {branch_name}{message} is caller-provided. Asked to author it → stop and surface: "Commit message authoring is out of scope — provide a message or use a commit-message skill."
Delete Branch
git push origin --delete {branch}remote ref does not exist → treat as success, skip silently. Any other error surfaces.
Delete All Story Branches
gh api --paginate repos/{owner}/{repo}/branches --jq '.[].name'- Filter for
feature/issue-{N}-*,fix/issue-{N}-*, orrevert/issue-{N}-*. - Confirm the full delete list, then delete each via
git push origin --delete {branch}(skip silently on "remote ref does not exist"). - Report: count deleted, count skipped, failures.
Create PR
gh pr create --repo {owner}/{repo} --title "{title}" --body "{body}" --head {head} --base {base}— returns PR URL.bodyrendered viagithub-templates(e.g.pr-story,pr-bug) — never freeform.- Resolve the number from the URL or
gh pr view {url} --json number,url. Report both number and URL.
Fetch PR
gh pr view {id} --repo {owner}/{repo} --json title,body,headRefName,baseRefName,files,merged,closingIssuesReferences- Also
gh pr diff {id}for file list and diff content.
List PRs
gh pr list --repo {owner}/{repo} --state {state} --json number,title,url,headRefName,state,mergedstate:open|closed|merged|all. "Merged only" →--state merged.
Submit Review
- Approve:
gh pr review {pr_id} --approve --body "{body}" - Request changes:
gh pr review {pr_id} --request-changes --body "{body}" {body}for structured reviews rendered viagithub-templates.
Merge PR
gh pr merge {pr_id} --repo {owner}/{repo} --squash
Diff Branch Files
gh api repos/{owner}/{repo}/compare/{base}...{head} --jq '[.files[].filename]'— array of changed file paths.
Multi-codebase Operations
Resolve owner/repo per codebase → build full mutation plan across all → run Confirmation Protocol once with combined list → execute per codebase sequentially (parallel pushes can race) → aggregate per-codebase success/skip/error into one summary.
Constraints
- Never hardcode
owner/repo— always derive viagh repo viewfrom the codebase directory. - Never write commit message content — the caller provides
{message}. - Never write PR or review body content from scratch — render via
github-templates. - Never auto-create missing base branches — stop and surface.
- Never run mutating ops without confirmation, even from a higher-level orchestrator.
- Never silently swallow errors other than
remote ref does not existon delete. - Never operate on a codebase whose path isn't in the Codebases table.
- Force pushes require explicit caller request plus confirmation — never inferred.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

