agentleFS
alamenaialamenai/terrae/.claude/skills/issue/SKILL.md

issue

Skill245 starsChanged 9 months agoMITView on GitHub

Read a GitHub issue, summarize it, and create a branch for it

53 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use branch, backlog and 5 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.
  • MindgamesSkill

    branch

    Use when a user asks to create a new local git branch and start issue work (for example, "create branch" or "start working on issue XYZ"). Use this for issue-based branch naming in the `type/scope-short-description` pattern and for always syncing local `main` from `origin/main` before creating the new branch, creating the local tracking `main` branch first when needed.

    Also in 3 projects that use this

  • vertz-devSkill

    backlog

    Manages deferred/blocked work items as GitHub Issues with labels and blocker tracking

    Also in 3 projects that use this

  • CodeWithBehnamSkill

    browse

    Fast headless browser for QA testing and site dogfooding. Navigate any URL, interact with elements, verify page state, diff before/after actions, take annotated screenshots, check responsive layouts, test forms and uploads, handle dialogs, and assert element states. ~100ms per command. Use when you need to test a feature, verify a deployment, dogfood a user flow, or file a bug with evidence.

    Also in 3 projects that use this

  • lukeleekrSkill

    scout

    GitHub 레포 스카우터. 내 Claude Code + Codex App 환경을 분석하여 필요한 GitHub 레포를 자동 추천하거나, 키워드로 GitHub을 검색합니다. "scout", "스카우트", "깃헙 탐방", "레포 추천", "repo search" 등의 키워드에 반응합니다.

    Also in 3 projects that use this

  • sunnyclinches44Skill

    explain

    Explains code using real-world analogies and ASCII diagrams

    Also in 4 projects that use this

  • VercelSkill

    deploy

    Deploy applications to Vercel. Use when the user says "deploy", "deploy to Vercel", "push to production", "deploy my app", or "go live".

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 4 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 51 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read a GitHub issue by number or URL, summarize it, then create a working branch.

    line 9
  2. Distinctive:

    If a URL is provided, extract the issue number from it.

    line 22
  3. Very specific:

    Run gh issue view <number> --repo alamenai/terrae to read the issue

    line 27
  4. Distinctive:

    If the issue doesn't exist, tell the user and stop

    line 28
  5. Distinctive:

    Keep the description part short (2-4 words, kebab-case)

    line 43
  6. Very specific:

    Make sure we're on main and up to date: git checkout main && git pull

    line 50
  7. Very specific:

    Create and switch to the new branch: git checkout -b <branch-name>

    line 51

“Common” is measured: kept by at least 6 in 10 of the 51 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

Issue Skill

Read a GitHub issue by number or URL, summarize it, then create a working branch.

Repository

alamenai/terrae — https://github.com/alamenai/terrae/issues

Arguments

The user provides either:

  • An issue number (e.g., 42)
  • A GitHub issue URL (e.g., https://github.com/alamenai/terrae/issues/42)

If a URL is provided, extract the issue number from it.

Instructions

  1. Fetch the Issue
    • Run gh issue view <number> --repo alamenai/terrae to read the issue
    • If the issue doesn't exist, tell the user and stop
  2. Summarize the Issue
    • Display the issue title and number
    • Summarize the description in 2-3 bullet points
    • List any labels
    • Note if there are linked PRs or assignees
  3. Determine Branch Name
    • Infer the type from labels or content:
      • bug label or bug description → fix/
      • enhancement or feature label → feat/
      • documentation label → docs/
      • Otherwise → feat/
    • Build the branch name: type/issue-number-short-description
    • Keep the description part short (2-4 words, kebab-case)
    • Examples:
      • feat/42-add-heatmap-component
      • fix/17-marker-memory-leak
      • docs/8-update-installation-guide
  4. Create the Branch
    • Make sure we're on main and up to date: git checkout main && git pull
    • Create and switch to the new branch: git checkout -b <branch-name>
    • Confirm the branch was created
  5. Report
    • Show the branch name
    • Remind the user what the issue is about so they can start working

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.