agentleFS
Sign inStart free
aws-solutionsaws-solutions/konductor/skills/git-workflow/SKILL.md

git-workflow

Skill11 starsChanged 49 days agoApache-2.0View on GitHub

Git workflow patterns for atomic commits, branch management, and history operations. Use when committing changes, managing branches, or searching git history.

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

6 rules. 0 are common, 6 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 165 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when:

    line 16
  2. Distinctive:

    Never mix formatting changes with logic changes

    line 32
  3. Distinctive:

    Every commit must compile and pass tests

    line 57
  4. Distinctive:

    Keep branches short-lived — merge within days, not weeks

    line 63
  5. Distinctive:

    Use git status and git diff first to get current status, then targeted git commands for deeper investigation.

    line 76
  6. Distinctive:

    IMPORTANT: Commit message not following conventional format.

    line 88

“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

Git Workflow

Overview

Standard git workflow patterns for atomic commits, branch management, and history operations. Ensures clean, traceable history across projects.

Usage

Use this skill when:

  • Committing changes to a repository
  • Creating or managing feature branches
  • Searching git history for debugging or auditing
  • Reviewing what changed before submitting a pull request

Commit Standards

Atomic Commits

Each commit must contain exactly one logical change. Split work into separate commits:

  • One commit per bug fix
  • One commit per feature addition
  • One commit per refactor
  • Never mix formatting changes with logic changes

Conventional Commit Messages

Format: <type>(<scope>): <description>

TypeWhen to Use
featNew feature or capability
fixBug fix
refactorCode restructuring without behavior change
testAdding or updating tests
docsDocumentation changes
choreBuild config, dependencies, tooling

Examples:

  • feat(api): add ListNetworkDevices operation
  • fix(dynamodb): add condition expression to prevent overwrites
  • refactor(handler): extract validation into shared utility

Commit Hygiene

  • Imperative mood: "add feature" not "added feature"
  • Subject line under 72 characters
  • Every commit must compile and pass tests

Branch Management

  • Branch from main for new work
  • Naming: <type>/<short-description> (e.g., feat/network-monitoring, fix/throttling-retry)
  • Keep branches short-lived — merge within days, not weeks
  • Rebase on main before submitting a PR

History Operations

CommandPurpose
git log --oneline -20Recent commit history
git log --author=<alias>Commits by author
git blame <file>Line-by-line attribution
git bisect start/bad/goodBinary search for regression
git log -S "<string>"Find commits that added/removed a string

Use git status and git diff first to get current status, then targeted git commands for deeper investigation.

Tools

ToolPurpose
Shell (git)Direct git commands for history, blame, bisect

Quality Gate

CRITICAL: Non-atomic commit mixing unrelated changes. Commit that breaks compilation or tests. Committing secrets or credentials.

IMPORTANT: Commit message not following conventional format. Branch not rebased before PR. Feature branch older than 2 weeks without merge.

SUGGESTION: Could improve commit message description. Could split large commit further.

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