agentleFS
Sign inStart free
alphacrackalphacrack/readme2demo/.claude/skills/git-github-operator/SKILL.md

git-github-operator

Skill9 starsChanged 4 months agoMITView on GitHub

Git and GitHub operations for maintaining the readme2demo repo — branching, conventional commits, PRs, releases, and the never-commit rules. Use when committing, opening a PR, tagging a release, or doing any git/gh operation on this repo.

  • Reads credentials
  • Commits and pushes

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    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. Distinctive:

    When a commit fixes a failure class, name the run that found it and note the regression test.

    line 25
  2. Very specific:

    Run the /ship-check command (or the ship-check flow): tests green, compile clean, grounding-auditor on any src change touching the …

    line 31
  3. Very specific:

    Run dirs are disposable and gitignored.

    line 54

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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 & GitHub operator for readme2demo

Remote: https://github.com/alphacrack/readme2demo (origin). Default branch: main. In non-interactive sessions you can stage/commit locally but the human runs git push (auth lives on their machine).

Never commit

  • runs/ — every pipeline run (transcripts, videos, cloned repos, and potentially the target repo's content). Gitignored; keep it that way. Publishable examples are HAND-COPIED into examples/ after review.
  • .env, readme2demo.toml, any credential. Before every commit: git diff --cached | grep -iE 'sk-ant-[a-z0-9]{8}' must be empty, and git status --short | grep runs/ must be empty.

Commit style

Conventional-ish, imperative subject, then a body that lists WHAT changed and WHY — this repo's history is a design log (read git log to see the bar). When a commit fixes a failure class, name the run that found it and note the regression test. One concern per commit where practical; batch tightly-coupled changes (code + test + CLAUDE.md entry) together.

Pre-push gate

Run the /ship-check command (or the ship-check flow): tests green, compile clean, grounding-auditor on any src change touching the LLM→artifact path, hygiene greps. If images/base/Dockerfile changed, the commit body must tell users to rebuild (docker build --no-cache -t readme2demo/base:latest images/base/).

Branches & PRs

  • Feature work on a branch; PR into main. PR description states the failure class or feature, the systemic fix (code first), and the regression test.
  • CI (.github/workflows/ci.yml) runs the suite on 3.10 and 3.12 — a red CI blocks merge. Keep the suite docker/network/API-free so CI stays fast.
  • good first issue / help wanted labels are seeded for contributors (see launch/LAUNCH_CHECKLIST.md).

Releases

  • Tag vX.Y.Z with honest notes (state the MVP tradeoffs — Docker required, README treated as untrusted code, API key enters sandbox until the egress proxy lands). The pinned Claude Code version in the base image is coupled to the stream-json parser — call out a bump in the release notes.

Repairing a user's run without git

Run dirs are disposable and gitignored. To salvage a failed run, patch its commands.sh/plan.json or regenerate its guide+tape with the pure functions (see the debug-run skill) and give the resume --from-stage command — no commit involved.

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.

Check your setup, free