agentleFS
Sign inStart free
extra-orgextra-org/extra/.claude/skills/git-workflow/SKILL.md

git-workflow

Skill119 starsChanged 5 months agoMITView on GitHub

Work safely with Git — keep changes scoped and reviewable, never overwrite the user's work, and produce clear history. Use before editing, branching, staging, or committing.

  • 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

7 rules. 0 are common, 5 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 165 edited versions we read keep these.

  • 5

    Distinctive

    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
  • could be automatic: a setting could enforce it
  1. Very specific:

    Do not edit this file directly.

    line 10
  2. Distinctive:

    Before editing files (inspect current state first).

    line 23
  3. Distinctive:

    Inspect before editing: Run git status and git diff to understand uncommitted work.

    line 35
  4. Distinctive:

    Commit only when asked: Do not auto-commit; never force-push shared branches or skip hooks.

    line 39
  5. Distinctive:

    Clear messages: Use a conventional, scoped commit style.

    line 41
  6. Very specific:

    No secrets: Never stage .env, credentials, or large binaries.

    line 42
  7. Distinctive:

    Use a conventional prefix:

    line 56

“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
<!-- This file is generated by tools/skills. Do not edit this file directly. Edit .ai/skills/git-workflow.md and run `make generate-ai`. -->

Skill: Git Workflow

Purpose

Work safely with Git: keep changes scoped and reviewable, never overwrite the user's work, and produce clear history.

When to Use This Skill

  • Before editing files (inspect current state first).
  • Branching, staging, or committing.
  • Preparing a change set or pull request for review.

Files to Read First

  • AGENTS.md (git safety + scope rules).
  • docs/DEVELOPMENT_WORKFLOW.md.
  • The current diff/status of the repository.

Core Principles

  • Inspect before editing. Run git status and git diff to understand uncommitted work; never clobber the user's changes.
  • Keep changes scoped to one task; avoid massive unrelated diffs.
  • Don't reformat or move files outside scope.
  • Commit only when asked. Do not auto-commit; never force-push shared branches or skip hooks.
  • Clear messages. Use a conventional, scoped commit style.
  • No secrets. Never stage .env, credentials, or large binaries.

Process

  1. Inspect: git status and git diff (and git log --oneline -5 for message style). Note any pre-existing uncommitted work to preserve.
  2. Scope the change to the current task; keep unrelated edits out.
  3. Stage deliberately (git add <paths>) — review what's staged; ensure no secrets or ignored files sneak in.
  4. Commit when asked, using the format below and a HEREDOC for the message.
  5. Summarize the modified files in your final response.

Commit message format

Use a conventional prefix:

  • feat: a new feature/capability
  • fix: a bug fix
  • refactor: behavior-preserving restructuring
  • docs: documentation only
  • test: tests only
  • chore: tooling/config/housekeeping

Example: docs: consolidate agent instructions under .ai/

Checklist Before Finishing

  • Inspected git status/git diff before editing; no user work clobbered.
  • Change is scoped to one task; no unrelated churn.
  • No secrets, .env, or large binaries staged.
  • Commit message (if committing) uses the conventional format.
  • Only committed because the user asked.
  • Modified files summarized in the final response.

Common Mistakes to Avoid

  • Editing without first checking for uncommitted user work.
  • Sweeping reformat/rename diffs mixed with logic changes.
  • Committing secrets or ignored files.
  • Auto-committing when not asked, or force-pushing shared branches.
  • Vague commit messages with no scope/prefix.

Expected Final Report

State: the result of the pre-edit inspection; the list of modified/created files and how they map to the task; whether a commit was made (and its message); and confirmation that no secrets or out-of-scope changes were included.

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