agentleFS
TsukiNi22TsukiNi22/ai-utils/skills/routers/git/SKILL.md

git

Skill1 starsChanged 3 days agoMITView on GitHub

Router for git / GitHub tasks of the user - commit messages, branches, pull requests, tags, releases, CHANGELOG, repository setup, CI/CD workflows - loads git-conventions, git-commit, ci-cd, pre-commit (and the doc skills when a README/CHANGELOG is involved). Invoke manually with /git.

61 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use sql, databases and 10 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.
  • thechandanbhagatSkill

    sql

    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

  • mrgoonieSkill

    databases

    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

  • mrgoonieSkill

    devops

    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

  • MicrosoftSkill

    typescript

    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

  • VercelSkill

    react

    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 AzureSkill

    test

    Also in 8 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 55 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Never commit / push / tag / release / open a PR without an explicit request in the current message: write the message and suggest the …

    line 35
  2. Very specific:

    No AI attribution (Co-Authored-By, "Generated with") except where the user allowed it (the ai-utils repository).

    line 38
  3. Distinctive:

    Start the answer with one line listing the loaded skills.

    line 39

“Common” is measured: kept by at least 6 in 10 of the 55 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Git router

Request given with /git: $ARGUMENTS

Load the skills with the Skill tool (never the other routers: they are manual-only), then do the task. The request is the text given with /git (or the latest request; if none, run git status / git log --oneline -10 and propose: commit message for the pending changes, release, PR...).

Context

  • git status, git branch -a, git log --oneline -15, git remote -v, tags (git tag --sort=-creatordate | head).
  • Solo or team project: git shortlog -sn --all | head (team = several authors) -> branches/PR rules.
  • CI keywords used? grep -l "\[build\]\|\[release\]\|\[ignore\]" .github/workflows/* 2>/dev/null.

Skills

SituationSkills
commit the current changes / diff locally ("fais le commit", "commit tout"): grouped logical commits, title-only messages, no co-author, never pushedgit-commit (+ git-conventions)
commit message only, amend, branch name, tag, version bumpgit-conventions
release (tag + GitHub release + CHANGELOG)git-conventions (+ readme-style if the README changes)
pull request (team project only)git-conventions
CHANGELOG onlygit-conventions
new repository, branch protection, gh setupgit-conventions (+ cpp-project for a new C++ project)
CI / CD workflows, GitHub actions, the Docker images of the CIci-cd
pre-commit hook, style checked / commits blocked locally before the commitpre-commit

Always

  • Never commit / push / tag / release / open a PR without an explicit request in the current message: write the message and suggest the command otherwise. Asking to commit the current changes (git-commit) is that request for the local commits only; the push stays a suggestion.
  • No AI attribution (Co-Authored-By, "Generated with") except where the user allowed it (the ai-utils repository).
  • Start the answer with one line listing the loaded skills.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.