Skip to content

TsukiNi22/ai-utils / skills/routers/git

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.

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.
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 318kUpdated Claude CodeCodexUnverifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 117kUpdated Claude CodeCodexUnverifiedInstall