agentleFS
Sign inStart free
openfloconopenflocon/Flocon/.claude/skills/git-setup/SKILL.md

git-setup

Skill379 starsChanged 28 days agoMITView on GitHub

Use before starting work on a Flocon feature, and before creating a branch or a commit. Sets the branch name (the feature name, never `claude/`) and the commit message format. Runs in the Haiku `git-ops` agent: pass the feature name or what to commit as arguments.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. microsoft/hve-core★ 1.6ksame name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository4 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    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:

    Never claude/, worktree- or random suffixes.

    line 18
  2. Distinctive:

    Never commit on main.

    line 23
  3. Very specific:

    If the current branch starts with claude/ or worktree- and has not been pushed, rename it: git branch -m <type>/<feature-kebab>.

    line 24
  4. Distinctive:

    If it was already pushed or belongs to someone else, don't rename it.

    line 25
  5. Very specific:

    Never commit secrets, local.properties, signing keys or build outputs.

    line 35
  6. Very specific:

    No Claude attribution lines (no Co-Authored-By, no "Generated with").

    line 36

≈ “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 setup: branch & commit naming

Task from the caller: $ARGUMENTS

Branch

Format: <type>/<feature-kebab>

  • type is one of feat, fix, refact, perf, docs, test, chore (same as the commit prefix).
  • The rest is the feature name: lowercase kebab-case, 2 to 5 words.
  • Never claude/, worktree- or random suffixes.

Examples: feat/device-selector-logos, fix/network-clear-instant, chore/ktlint-multiline-if-else, feat/mcp-take-flocon-screenshot.

Steps:

  1. Never commit on main.
  2. If the current branch starts with claude/ or worktree- and has not been pushed, rename it: git branch -m <type>/<feature-kebab>.
  3. If it was already pushed or belongs to someone else, don't rename it; tell the user.

Commit message

Format: <type>: [AREA] imperative summary

  • Same type list as the branch.
  • [AREA] in caps, reusing the areas already in git log (MCP, NETWORK, DESIGN, TIMELINE, Desktop, OKHTTP...). Use feat(sample): ... for sample apps.
  • English, imperative, under 72 characters, no trailing period.
  • One logical change per commit; never mix formatting-only changes with behavior changes.
  • Never commit secrets, local.properties, signing keys or build outputs.
  • No Claude attribution lines (no Co-Authored-By, no "Generated with").

Good: feat: [MCP] list_images tool, fix: [NETWORK] Clear the list instantly when pressing the trash button. Bad: Update stuff, feat: added a new tool., fix(network): Fixes.

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