alamenai/terrae / .claude/skills/issue
issue
VerifiedRead a GitHub issue, summarize it, and create a branch for it
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.7 KB |
SKILL.md
View on GitHub---
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
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| add-product-e2e-evalpaperclipai/paperclipAdd or extend a Paperclip full-stack runner E2E workflow, fixture, matcher, or report evidence path for local or Daytona execution. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| add-runner-evalpaperclipai/paperclipAdd or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| diagnose-why-work-stoppedpaperclipai/paperclipCompatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use fix-failed-paperclip-run for the full diagnosis, regression, repair, real verification, and green-PR workflow; honor an explicitly requested diagnosis-only scope. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| fix-failed-paperclip-runpaperclipai/paperclipDiagnose and fix failed, stuck, slow, or incorrectly blocked Paperclip tasks and runs. Use with a task/run URL or failure report to trace the root cause, prove a regression red then green, check second-order effects, verify the real workflow, and deliver a PR with passing checks. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |