agentleFS
Sign inStart free
VPDPersonalVPDPersonal/Aspid.MVVM/.claude/skills/asp-branch/SKILL.md

asp-branch

Skill65 starsChanged 20 days agoMITView on GitHub

Git branch naming convention. Use when creating a branch or choosing its name.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    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
  1. Very specific:

    Use <type>/<short-description>, where <type> is the Conventional Commits type the commit or PR title will use:

    line 10
  2. Very specific:

    No author, agent or tool prefixes.

    line 30

≈ “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

Branch naming

Use <type>/<short-description>, where <type> is the Conventional Commits type the commit or PR title will use:

  • feat/ — new functionality.
  • fix/ — bug fixes.
  • perf/ — performance improvements.
  • refactor/ — restructuring without changing behavior.
  • style/ — formatting only.
  • docs/ — documentation.
  • test/ — tests.
  • build/ — build system and packaging.
  • ci/ — CI workflows.
  • chore/ — dependencies, tooling, and maintenance.
  • revert/ — reverting a previous change.

Description rules:

  • English, lowercase kebab-case, 2–5 words.
  • The whole name is 40 characters max.
  • Exactly one slash.
  • Describe the concrete change. Add the affected area only if the description alone does not show where the change is.
  • No author, agent or tool prefixes. No dates. No vague words such as final or working.

Examples: feat/generator-observable-properties, fix/handle-null-target, docs/update-installation.

git branch -m or git switch -c says the name exists? Add one word to the description and run again.

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