Agent skill

Issue

by alamenai in alamenai/terrae

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

MITAuto-check passedDevelopment

Install Issue

skills CLI
$ npx skills add alamenai/terrae --skill issue -a claude-code

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

GitHub CLI
$ gh skill install alamenai/terrae issue --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/alamenai/terrae.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/issue .claude/skills/issue && 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
issue
GitHub stars
244
Token cost
~425 tokens
SKILL.md length
198 words
Files
1
Skills in repo
11
Repo updated
First seen
Licence
MIT

At a glance

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

  • Works in 5 steps: Fetch the Issue → Summarize the Issue → Determine Branch Name → …
  • Development work in your project
  • SKILL.md covers Repository, Arguments and Instructions
  • Calls git and gh

What it does

Issue is an agent skill from alamenai/terrae. Read a GitHub issue, summarize it, and create a branch for it

Its SKILL.md is about 430 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, Mapbox, React and Git. The repository describes itself as: Composable and animated components that replace imperative layers with simple props. The perfect companion for shadcn/ui. The licence is MIT.

When your agent uses it

  • Development work in your project

Example prompts

  • “/issue”

Requirements

  • Pre-approved tools (allowed-tools): Bash(gh *), Bash(git *)

Workflow steps

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

  1. Fetch the Issue
  2. Summarize the Issue
  3. Determine Branch Name
  4. Create the Branch
  5. Report

What it can do on your machine

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

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash(gh *)
    • Bash(git *)

    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

Issue loads about 425 tokens when it runs. Until then it costs about 17 tokens; SKILL.md has 198 words of instructions outside code blocks.

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

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 alamenai/terrae at commit ea9a480, republished under its MIT licence (© alamenai). 198 words, ~425 tokens.

Download SKILL.mdSave it as .claude/skills/issue/SKILL.md (or your agent's skills folder).
name
issue
description
Read a GitHub issue, summarize it, and create a branch for it
allowed-tools
Bash(gh *), Bash(git *)

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

© alamenai, 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/issue of alamenai/terrae.

Open the folder on GitHubat commit ea9a480

Compare with similar skills

Issue 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.

Issue compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Issue this skillalamenai/terrae244—~425Automated safety check: PassMIT
Gh Release Notesreact-cosmos/react-cosmos8.7k—~335Automated safety check: PassMIT
Git Workflowbkywksj/knowledge-base330—~1.1kAutomated safety check: PassCustom licence
Fix GitHub IssueAgnosticUI/agnosticui827—~751Automated safety check: PassApache-2.0
Contributor-First PR MergeHKUDS/OpenHarness16k1 repos~847Automated safety check: PassMIT
Create Pull Requestcline/cline70k1 repos~1.6kAutomated safety check: PassApache-2.0

Similar skills

  • Gh Release Notes

    react-cosmos/react-cosmos

    Generate a clean list of commits between two git tags for GitHub release notes.

    8.7k GitHub stars~335 tokensUpdated 16 days ago
    DevelopmentAuto-check passed
  • Git Workflow

    bkywksj/knowledge-base

    Git 工作流与版本管理技能,规范分支策略、提交信息和发布流程. An agent skill from bkywksj/knowledge-base.

    330 GitHub stars~1.1k tokensUpdated 6 days ago
    DevelopmentAuto-check passed
  • Fix GitHub Issue

    AgnosticUI/agnosticui

    Fix a GitHub issue by number. An agent skill from AgnosticUI/agnosticui.

    827 GitHub stars~751 tokensUpdated today
    Frontend & DesignAuto-check passed
  • Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.

    16k GitHub starsUsed in 1 repo~847 tokens
    DevelopmentAuto-check passed
  • Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.

    70k GitHub starsUsed in 1 repo~1.6k tokens
    DevelopmentAuto-check passed
  • Pull Request Title and Body Writer

    openinterpreter/openinterpreter

    Rewrites the title and body of one or more pull requests with gh, leading with why the change was made, then what changed, and describing only the net result.

    69k GitHub starsUsed in 2 repos~1.1k tokens
    DevelopmentAuto-check passed

More from alamenai/terrae

All 11 skills in this repo
  • Check

    alamenai/terrae

    Verify all outputs exist after creating a new component and fix any issues

    244 GitHub stars~1.1k tokensUpdated 6 mo ago
    Auto-check passed
  • Docs

    alamenai/terrae

    Generate or update documentation for Terrae components. An agent skill from alamenai/terrae.

    244 GitHub stars~576 tokensUpdated 6 mo ago
    Auto-check passed
  • Fix

    alamenai/terrae

    Systematically fix issues found by /review or reported by the user

    244 GitHub stars~775 tokensUpdated 6 mo ago
    Auto-check passed
  • New

    alamenai/terrae

    End-to-end workflow for building a new Terrae component from scratch

    244 GitHub stars~2.4k tokensUpdated 6 mo ago
    Auto-check passed
  • Perf

    alamenai/terrae

    Audit component performance and identify optimization opportunities with actionable fixes

    244 GitHub stars~678 tokensUpdated 6 mo ago
    Auto-check passed
  • PR

    alamenai/terrae

    Commit, push, and open a pull request on GitHub. An agent skill from alamenai/terrae.

    244 GitHub stars~767 tokensUpdated 6 mo ago
    Auto-check: notes

Categories

Questions about Issue

What does Issue do?

Read a GitHub issue, summarize it, and create a branch for it. Issue is an agent skill from alamenai/terrae.

When should I use Issue?

Issue fits situations like: development work in your project.

How do I install Issue in Claude Code?

Run `npx skills add alamenai/terrae --skill issue -a claude-code`. Or copy the skill folder (.claude/skills/issue in alamenai/terrae) into .claude/skills/issue in your project. Claude Code loads it when a task matches its description.

How do I install Issue in Codex?

Run `npx skills add alamenai/terrae --skill issue -a codex`. Or copy the skill folder (.claude/skills/issue in alamenai/terrae) into .agents/skills/issue in your project. Codex loads it when a task matches its description.

Can I use Issue 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 alamenai/terrae --skill issue -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/issue, .gemini/skills/issue, .github/skills/issue and .opencode/skills/issue in your project.

What does Issue need to run?

Going by SKILL.md and its folder, Issue needs the command-line tools its instructions call (git and gh). Its frontmatter pre-approves these tools: Bash(gh *), Bash(git *).

Does Issue 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 Issue 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 Issue use?

Issue 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 Issue use?

About 425 tokens (SKILL.md is roughly 1.7k 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 Issue?

Skills that share tags, products or a category with Issue: Gh Release Notes (react-cosmos/react-cosmos, 8.7k stars), Git Workflow (bkywksj/knowledge-base, 330 stars), Fix GitHub Issue (AgnosticUI/agnosticui, 827 stars) and Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Issue?

alamenai (a GitHub user) maintains it in alamenai/terrae, which has 244 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on April 6, 2026.

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