agentleFS
kaka-rutokaka-ruto/skills/git-workflow/SKILL.md

git-workflow

Skill4 starsChanged 7 months agoMITView on GitHub

Use when doing any git operations (branching, committing, pushing) so the repo history stays clean and matches the preferred workflow

  • Deletes or force-pushes
  • Commits and pushes

187 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use squad-commands, ci-cd-pipelines 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.
  • Microsoft AzureSkill

    squad-commands

    Categorized catalog of common Squad operations. Coordinator reads this file and presents it as an interactive menu when the user asks for available commands or help.

    Also in 5 projects that use this

  • harrissohail6Skill

    ci-cd-pipelines

    CI/CD pipeline design and implementation. Auto-activates when discussing deployment, automation, or pipelines.

    Also in 6 projects that use this

  • Microsoft AzureSkill

    architectural-proposals

    How to write comprehensive architectural proposals that drive alignment before code is written

    Also in 4 projects that use this

  • frostneySkill

    native-nostalgia-stack

    Applies the user's FreePascal toolchain and its build, formatting, hook, and test contracts while leaving project-specific mechanics local. Use when scaffolding or working in a FreePascal project that follows this toolchain.

    Also in 3 projects that use this

  • AGMO-IncSkill

    plugin-review

    Use to analyze plugin usage patterns and suggest improvements. Triggers on "플러그인 리뷰", "plugin review", "사용 패턴 분석".

    Also in 3 projects that use this

  • Galaxy-DawnSkill

    results-report

    This skill should be used when the user asks to "write an experiment report", "summarize experimental results", "do experiment retrospection", "write a results report", "写实验总结报告", "写实验复盘", or mentions turning completed experiment artifacts into a structured, decision-oriented research report. It assumes strict analysis should come from `results-analysis` first.

    Also in 3 projects that use this

  • +6 more from Azure

The file

Show its rules and text

We split this skill into the rules it gives an agent

25 rules. 0 are common, 22 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 164 edited versions we read keep these.

  • 22

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Only stop to report progress under exactly two conditions:

    line 14
  2. Distinctive:

    Do not create branches “just in case”.

    line 22
  3. Distinctive:

    If asked to create a branch, use a plain branch name with no tool/model prefixes.

    line 23
  4. Very specific:

    Do not prefix with codex/, claude/, agent/, etc.

    line 24
  5. Distinctive:

    Commit only complete slices: done, verified, and ready to ship.

    line 25
  6. Very specific:

    Commit messages are short plain sentences (no feat:, chore:, etc.).

    line 26
  7. Distinctive:

    Prefer a single sentence.

    line 27
  8. Distinctive:

    If needed, use 2–3 short sentences total (no paragraphs).

    line 28
  9. Distinctive:

    Never use git add .. Always stage by explicit filenames to avoid accidental commits.

    line 29
  10. Distinctive:

    Check working tree state: git status

    line 41
  11. Distinctive:

    Only create a branch when explicitly asked.

    line 46
  12. Distinctive:

    Keep branch names simple and descriptive, like:

    line 47
  13. Distinctive:

    Do not commit partial work, experiments, or “WIP” unless the human explicitly asks.

    line 55
  14. Distinctive:

    If a change is essentially “more of the same” as the most recent commit (tight follow-up, fixup, small adjustment), prefer amending the …

    line 56
  15. Distinctive:

    If it is unclear whether to amend vs make a new commit, ask.

    line 57
  16. Very specific:

    Do not add co-authoring trailers (no Co-authored-by:).

    line 58
  17. Distinctive:

    Pushing to master triggers a deploy: Treat git push as a production operation.

    line 76
  18. Distinctive:

    Do not push to master unless you are intentionally deploying to production.

    line 80
  19. Distinctive:

    Only push to master when all unpushed commits are complete, verified, and safe for production.

    line 84
  20. Distinctive:

    Do not push if there are missing dependencies, unfinished work, or “it should work” assumptions.

    line 85
  21. Distinctive:

    If the change set is not ready to deploy, keep commits local until it is ready.

    line 86
  22. Distinctive:

    If the work is finished and verified, prefer pushing and deploying rather than accumulating completed work locally without a reason.

    line 87
  23. Distinctive:

    Only push to master when ready to release a new version.

    line 91
  24. Distinctive:

    Never run destructive git commands (git reset --hard, forced checkouts, force pushes) unless explicitly requested and confirmed.

    line 96
  25. Distinctive:

    If unrelated changes exist in the worktree, do not revert them unless asked.

    line 97

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

Overview

This skill defines the default git workflow for this environment: work directly on master unless explicitly asked otherwise, keep branches unprefixed, and commit only complete, verified slices with short commit messages.

Important: git work (staging/committing/pushing, etc) is not a signal to stop or report progress. After any commit, immediately return to the continuous loop: pick the next top-most unchecked PLAN.md Now item and keep going.

Only stop to report progress under exactly two conditions:

  • All PLAN.md Now work is complete, or
  • A hard blocker / high-risk gate / product decision is encountered.

Defaults (Rules)

  • Work on master unless the human explicitly asks for a new branch.
  • Do not create branches “just in case”.
  • If asked to create a branch, use a plain branch name with no tool/model prefixes.
    • Do not prefix with codex/, claude/, agent/, etc.
  • Commit only complete slices: done, verified, and ready to ship.
  • Commit messages are short plain sentences (no feat:, chore:, etc.).
    • Prefer a single sentence.
    • If needed, use 2–3 short sentences total (no paragraphs).
  • Never use git add .. Always stage by explicit filenames to avoid accidental commits.

Before Any Commit

Confirm the slice is complete:

  • The intended outcome is achieved.
  • Verification was run (tests or the project’s chosen verification step).
  • Any required checklist/docs updates for the slice are included.

Then:

  • Check working tree state: git status
  • Review diff: git diff (and git diff --staged after staging)

Branching Rules

  • Only create a branch when explicitly asked.
  • Keep branch names simple and descriptive, like:
    • fix-login-timeout
    • billing-webhook-hardening
    • upgrade-rails-8

Commit Rules

  • One commit per completed slice whenever feasible.
  • Do not commit partial work, experiments, or “WIP” unless the human explicitly asks.
  • If a change is essentially “more of the same” as the most recent commit (tight follow-up, fixup, small adjustment), prefer amending the most recent commit instead of making a new commit.
    • If it is unclear whether to amend vs make a new commit, ask.
  • Do not add co-authoring trailers (no Co-authored-by:). The human is the sole author.

Commit Message Style

Good:

  • Fix login redirect loop
  • Add read-only admin audit view
  • Reduce flaky checkout test timeouts

Avoid:

  • feat: add admin audit view
  • chore: stuff
  • Long multi-paragraph explanations

Pushing

Pushing to master triggers a deploy. Treat git push as a production operation.

Hard gate:

  • Do not push to master unless you are intentionally deploying to production.

Rules:

  • Only push to master when all unpushed commits are complete, verified, and safe for production.
  • Do not push if there are missing dependencies, unfinished work, or “it should work” assumptions.
  • If the change set is not ready to deploy, keep commits local until it is ready.
  • If the work is finished and verified, prefer pushing and deploying rather than accumulating completed work locally without a reason.

Gems/libraries:

  • Only push to master when ready to release a new version.
  • It is acceptable to keep collecting local commits until release-ready.

Safety Defaults

  • Never run destructive git commands (git reset --hard, forced checkouts, force pushes) unless explicitly requested and confirmed.
  • If unrelated changes exist in the worktree, do not revert them unless asked. Keep your work focused.

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.