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.

MITAuto-check passedDevelopment

Install Branch Check

skills CLI
$ npx skills add ossappscollective/oss-weather --skill branch-check -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install ossappscollective/oss-weather branch-check --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/ossappscollective/oss-weather.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/branch-check .claude/skills/branch-check && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
branch-check
GitHub stars
456
Token cost
~356 tokens
SKILL.md length
174 words
Files
1
Skills in repo
8
Repo updated
First seen
Licence
MIT

At a glance

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.

  • Works in 7 steps: Check the current branch (git branch… → If you are on main, you must branch —… → Ensure main is current first: git pull… → …
  • Development work in your project
  • Calls git and gh

What it does

Branch Check is an agent skill from ossappscollective/oss-weather. 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.

Its SKILL.md is about 360 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development. It works with GitHub and iOS. The repository describes itself as: An OSS weather app for iOS/Android. The licence is MIT.

When your agent uses it

  • Development work in your project

Example prompts

  • “/branch-check”

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  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
  5. If no issue is in play, name the branch / from the change itself (e.g. feat/date-picker-range).
  6. Resolve the branch
  7. Check out the branch BEFORE planning. Interactive: confirm the branch name with the user first. --auto (caller runs autonomously): skip…

What it can do on your machine

Read from SKILL.md and the folder at commit 42715ad. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • gh

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git and gh, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Branch Check loads about 356 tokens when it runs. Until then it costs about 38 tokens; SKILL.md has 174 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~38
When it runs · the whole SKILL.md, loaded when a task matches
~356

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from ossappscollective/oss-weather at commit 42715ad, republished under its MIT licence (© ossappscollective). 174 words, ~356 tokens.

Download SKILL.mdSave it as .claude/skills/branch-check/SKILL.md (or your agent's skills folder).
name
branch-check
description
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.
disable-model-invocation
true

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.

© ossappscollective, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/branch-check of ossappscollective/oss-weather.

Open the folder on GitHubat commit 42715ad

Compare with similar skills

Branch Check next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Branch Check compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Branch Check this skillossappscollective/oss-weather456—~356Automated safety check: PassMIT
Store Submitzhitongblog/solomd1.2k—~1.7kAutomated safety check: NotesMIT
Releasedoronz88/pymobiledevice32.9k—~944Automated safety check: PassGPL-3.0
iOS FixMacMagazine/app-iOS171—~957Automated safety check: PassNone
Fix GitHub IssueShopify/flash-list7.2k—~1.6kAutomated safety check: PassMIT
PR Workflowkmworks/kmreader111—~899Automated safety check: PassMIT

Similar skills

  • Store Submit

    zhitongblog/solomd

    Publish a SoloMD release to the stores that have no usable submission API — Google Play Console and Microsoft Partner Center — by driving them through the local Unzoo Browser REST API.

    1.2k GitHub stars~1.7k tokensUpdated today
    DevelopmentAuto-check: notes
  • Release

    doronz88/pymobiledevice3

    Cut a new pymobiledevice3 release — create the GitHub release (which publishes to PyPI) with a curated Highlights section.

    2.9k GitHub stars~944 tokensUpdated yesterday
    DevelopmentAuto-check passed
  • iOS Fix

    MacMagazine/app-iOS

    Bug-fix and refactoring workflow for MacMagazine — root cause analysis, pattern-matching fix, regression verification.

    171 GitHub stars~957 tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Fix GitHub Issue

    Shopify/flash-list

    Official

    Full workflow for fixing a GitHub issue - understand the problem, reproduce, diagnose root cause, fix, test on iOS/Android simulators, review, and raise a PR

    7.2k GitHub stars~1.6k tokensUpdated 8 days ago
    DevelopmentAuto-check passed
  • PR Workflow

    kmworks/kmreader

    Create and merge KMReader GitHub pull requests. An agent skill from kmworks/kmreader.

    111 GitHub stars~899 tokensUpdated today
    DevelopmentAuto-check passed
  • Reviewing Changes

    bitwarden/ios

    Official

    Performs comprehensive code reviews for Bitwarden iOS projects, verifying architecture compliance, style guidelines, compilation safety, test coverage, and security requirements.

    696 GitHub stars~1.1k tokensUpdated today
    DevelopmentAuto-check passed

More from ossappscollective/oss-weather

All 8 skills in this repo
  • Commit

    ossappscollective/oss-weather

    MANDATORY skill for ALL commits. An agent skill from ossappscollective/oss-weather.

    456 GitHub stars~1.3k tokensUpdated today
    Auto-check passed
  • Open PR

    ossappscollective/oss-weather

    MANDATORY skill for ALL pull requests. An agent skill from ossappscollective/oss-weather.

    456 GitHub stars~918 tokensUpdated today
    Auto-check passed
  • Feat

    ossappscollective/oss-weather

    Build a feature end-to-end (GitHub issue or free-text → plan → implement → PR), OR plan one read-only with --investigate.

    456 GitHub stars~3.9k tokensUpdated today
    Auto-check: warnings
  • Fix

    ossappscollective/oss-weather

    Debug and fix any non-trivial issue end-to-end, OR triage a GitHub bug issue read-only.

    456 GitHub stars~4.2k tokensUpdated today
    Auto-check: warnings
  • Investigate Contract

    ossappscollective/oss-weather

    Read-only guarantee + interactive-vs-autonomous (--auto) behavior for investigate modes.

    456 GitHub stars~803 tokensUpdated today
    Auto-check passed
  • Understand Project

    ossappscollective/oss-weather

    Ground a feature or fix in existing code before planning or building — find a similar pattern, identify reusable assets, map the touch surface.

    456 GitHub stars~576 tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Branch Check

What does Branch Check do?

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. Branch Check is an agent skill from ossappscollective/oss-weather. 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.

When should I use Branch Check?

Branch Check fits situations like: development work in your project.

How do I install Branch Check in Claude Code?

Run `npx skills add ossappscollective/oss-weather --skill branch-check -a claude-code`. Or copy the skill folder (.claude/skills/branch-check in ossappscollective/oss-weather) into .claude/skills/branch-check in your project. Claude Code loads it when a task matches its description.

How do I install Branch Check in Codex?

Run `npx skills add ossappscollective/oss-weather --skill branch-check -a codex`. Or copy the skill folder (.claude/skills/branch-check in ossappscollective/oss-weather) into .agents/skills/branch-check in your project. Codex loads it when a task matches its description.

Can I use Branch Check in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ossappscollective/oss-weather --skill branch-check -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/branch-check, .gemini/skills/branch-check, .github/skills/branch-check and .opencode/skills/branch-check in your project.

What does Branch Check need to run?

Going by SKILL.md and its folder, Branch Check needs the command-line tools its instructions call (git and gh).

Does Branch Check access the network?

SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Branch Check safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Branch Check use?

Branch Check is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Branch Check use?

About 356 tokens (SKILL.md is roughly 1.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Branch Check?

Skills that share tags, products or a category with Branch Check: Store Submit (zhitongblog/solomd, 1.2k stars), Release (doronz88/pymobiledevice3, 2.9k stars), iOS Fix (MacMagazine/app-iOS, 171 stars) and Fix GitHub Issue (Shopify/flash-list, 7.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Branch Check?

ossappscollective (a GitHub organization) maintains it in ossappscollective/oss-weather, which has 456 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on October 9, 2026.

Source: ossappscollective/oss-weather on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.