agentleFS
Sign inStart free
AkylasAkylas/oss-weather/.claude/skills/branch-check/SKILL.md

branch-check

Skill459 starsChanged 3 months agoMITView on GitHub

Ensure you're on a correct working branch off up-to-date main before planning or editing — starting from a GitHub issue when one is in play.

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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
  1. Distinctive:

    Run before anything else, before planning or editing.

    line 7
  2. Distinctive:

    Check the current branch (git branch --show-current).

    line 9
  3. Distinctive:

    If you are on main, you must branch — never edit directly on main.

    line 10
  4. Very specific:

    Ensure main is current first: git pull origin main (rebase onto upstream/main if working from a fork).

    line 11
  5. Very specific:

    If a GitHub issue is in play, fetch it with gh and derive the branch from it:

    line 12
  6. Very specific:

    If no issue is in play, name the branch <type>/<short-description> from the change itself (e.g.

    line 16
  7. Distinctive:

    If it already exists, check it out.

    line 18
  8. Very specific:

    Check out the branch BEFORE planning.

    line 20

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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

Run before anything else, before planning or editing.

  1. Check the current branch (git branch --show-current).
  2. If you are on main, you must branch — never edit directly on main.
  3. Ensure main is current first: git pull origin main (rebase onto upstream/main if working from a fork).
  4. If a GitHub issue is in play, fetch it with gh and derive the branch from it:
    • gh issue view <number> --json number,title,labels — read the title and labels
    • Pick the <type> from the labels/intent (fix for a bug, feat for an enhancement, etc.)
    • Build the name as <type>/<number>-<slug>, where <slug> is the issue title lowercased, non-alphanumerics → -, trimmed (e.g. issue #1234 "ScrollView insets wrong on iOS" → fix/1234-scrollview-insets-wrong-on-ios)
  5. If no issue is in play, name the branch <type>/<short-description> from the change itself (e.g. feat/date-picker-range).
  6. Resolve the branch:
    • If it already exists, check it out.
    • Otherwise create it from up-to-date main.
  7. Check out the branch BEFORE planning. Interactive: confirm the branch name with the user first. --auto (caller runs autonomously): skip confirmation, just check out.

Download now (ZIP)

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 1

    1. Akylas/OSS-DocumentScanner★ 2.6k98% same

    Wrote their own version · 0

    None found.

    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 repository11 other files it gives its agents.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

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