gitgud
Git skills for coding agents: commits, branches, PRs, releases and going public, like a careful maintainer
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Check it deeper on your machine
It has changed since its scan on 19 Nov 2026.
As a Claude Code plugin, install it and then ask Claude Code:
/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/n-stau/gitgud with scanskillsafety
Or from a terminal, clone it and run it:
git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/n-stau/gitgud'
It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.
Badge for your README
Markdown
[](/listings/n-stau--gitgud)HTML
<a href="/listings/n-stau--gitgud"><img src="/api/listings/n-stau--gitgud/badge.svg" alt="findsafeskills safety rating" /></a>Install
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
git clone https://github.com/n-stau/gitgud.git cd gitgud ./install.sh
The script symlinks every skill into `~/.claude/skills` and `~/.agents/skills`. Requires git 2.40+, Python 3.9+ and, for pull requests and releases, the [GitHub CLI](https://cli.github.com).
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
README.md · README · 66 lines
- <div align="center">
- <img src="assets/icon.svg" alt="gitgud icon: a pixel git branch with a crown" width="112" height="112" />
- # gitgud
- gitgud is a pack of git skills for coding agents that commits, branches, reviews, releases and publishes like a careful maintainer.
-   
- [Installation](#installation) · [Skills](#skills) · [Safety](#safety)
- </div>
- ## Highlights
- - **Clean commits**: splits mixed work into logical Conventional Commits, matches the repo's own message style, keeps required trailers.
- - **Nothing private slips in**: every commit checks for `.env` files, keys, large binaries and debug leftovers; `scrub-private-data` scans the full history, commit metadata and photo EXIF/GPS.
- - **Branches without drama**: rebase or merge chosen by whether the branch is shared, conflict workflow, squash-merge-aware cleanup, reflog recovery.
- - **Releases from history**: next semver version and a Keep a Changelog section generated from commits by a stdlib-only script.
- - **Ready to open source**: a guided checklist from secret scan to license, README and replacing the old history on GitHub.
- - **Asks before it rewrites**: force pushes, history rewrites, deletes and visibility changes always need your explicit yes.
- ## Installation
- ```bash
- git clone https://github.com/n-stau/gitgud.git
- cd gitgud
- ./install.sh
- ```
- The script symlinks every skill into `~/.claude/skills` and `~/.agents/skills`. Requires git 2.40+, Python 3.9+ and, for pull requests and releases, the [GitHub CLI](https://cli.github.com).
- ## Quick start
- Skills load on their own when a request matches. Just ask:
- ```text
- commit my work
- clean up my merged branches
- open a PR for this
- cut a release
- make this repo ready to go public
- ```
- ## Skills
- | Skill | Purpose |
- |---|---|
- | `gitgud-commit` | Logical commits with Conventional Commits messages and a pre-commit safety check |
- | `gitgud-branch` | Naming, staying up to date, conflicts, worktrees, cleanup and recovery |
- | `gitgud-pr` | Self-review, PR title and body, splitting, review replies, merge and cleanup |
- | `gitgud-release` | Semver bump, changelog, manifest versions, annotated tag and GitHub release |
- | `gitgud-go-public` | Release-readiness checklist for publishing a private repo |
- | `scrub-private-data` | Find and remove secrets, personal data and metadata in files and full history |
- | `write-readme` | READMEs in the style of big-company open-source repos |
- ## Safety
- - Read-only by default: scans and dry runs never change the repo.
- - One yes per destructive step: force push, history rewrite, branch or repo deletion, tag push, release, visibility change.
- - Backups before rewrites, secrets never printed in full, nothing pushed unless you ask.
- ## License
- [MIT](LICENSE) © n-stau
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.