agentleFS
Sign inStart free
MoeenNehzatiMoeenNehzati/famulus/skills/git-workflow/SKILL.md

git-workflow

Skill4 starsChanged 4 months agoMITView on GitHub

Use when a task will edit a Git repository or the user asks to inspect or change Git state. Do not use solely because a read-only task happens inside a repository.

  • Reads credentials

188 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

  • GitHubSkill

    e2e-template-testing

    End-to-end validation of coordinator and agent template changes

    Also in 3 projects that use this

  • GitHubSkill

    notification-routing

    Route agent notifications to specific channels by type — prevent alert fatigue from single-channel flooding

    Also in 3 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

  • +5 more from Azure
  • +1 more from github

The file

We split this skill into the rules it gives an agent

12 rules. 0 are common, 11 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 165 edited versions we read keep these.

  • 11

    Distinctive

    This author's own choices. Worth a look.

  • 1

    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:

    Before editing files in any repo, verify it is on a named branch:

    line 15
  2. Distinctive:

    If this fails, the repo is in detached HEAD — check out a named branch before doing anything.

    line 21
  3. Distinctive:

    At session start: run this in both the skills repo and the CWD repo (if any).

    line 23
  4. Distinctive:

    Never create commits, amend, or push unless explicitly asked.

    line 27
  5. Distinctive:

    When a stable checkpoint is reached (completed subsection, resolved issue, passing tests, finished feature), note that it may be a good …

    line 28
  6. Distinctive:

    When approved: help with staging specific files, drafting the commit message, and exact steps.

    line 29
  7. Distinctive:

    Before staging, committing, restoring, stashing, or otherwise modifying git state, distinguish current-session changes from pre-existing or …

    line 34
  8. Distinctive:

    Do not stage, commit, restore, revert, stash, or otherwise touch unrelated dirty state unless the user explicitly asks for that scope.

    line 36
  9. Distinctive:

    If ownership is ambiguous, ask before acting on the ambiguous paths.

    line 37
  10. Very specific:

    Never use --no-verify or --no-gpg-sign unless explicitly asked.

    line 42
  11. Distinctive:

    Never force-push to main/master.

    line 43
  12. Distinctive:

    Prefer new commits over amending, especially after a hook failure.

    line 44

“Common” is measured: kept by at least 6 in 10 of the 165 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
<!-- BEGIN BLUEPRINT INTERFACES -->

Generated from blueprint.yaml. Do not edit this block by hand.

Used Interfaces: none

<!-- END BLUEPRINT INTERFACES -->

Branch safety (always check first)

Before editing files in any repo, verify it is on a named branch:

git symbolic-ref HEAD

If this fails, the repo is in detached HEAD — check out a named branch before doing anything. Do not edit and then discover the work can't land.

At session start: run this in both the skills repo and the CWD repo (if any). If either is detached, check out the default branch first.

Commit rules

  • Never create commits, amend, or push unless explicitly asked.
  • When a stable checkpoint is reached (completed subsection, resolved issue, passing tests, finished feature), note that it may be a good time to commit — but do not act without approval.
  • When approved: help with staging specific files, drafting the commit message, and exact steps.

Change ownership

  • Unless the user explicitly says otherwise, interpret "changes" as the changes made in the current assistant session.
  • Before staging, committing, restoring, stashing, or otherwise modifying git state, distinguish current-session changes from pre-existing or unrelated dirty work.
  • Tell the user when unrelated dirty state exists, including the affected paths or areas at a useful level of detail.
  • Do not stage, commit, restore, revert, stash, or otherwise touch unrelated dirty state unless the user explicitly asks for that scope.
  • If ownership is ambiguous, ask before acting on the ambiguous paths.

Commit hygiene

  • Stage specific files by name; avoid git add -A or git add . (risk of including .env, credentials, or large binaries).
  • Never use --no-verify or --no-gpg-sign unless explicitly asked.
  • Never force-push to main/master; warn if asked.
  • Prefer new commits over amending, especially after a hook failure.

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