Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

Commencer

gh-issue

Étoiles419

Forks51

Mis à jour14 mars 2026 à 13:01

Fetch GitHub issue, create branch, plan and implement with TDD, then open PR

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

TypedDevs

TypedDevs/bashunit

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

name	gh-issue
description	Fetch GitHub issue, create branch, plan and implement with TDD, then open PR
user-invocable	true
argument-hint	<issue-number>
allowed-tools	Bash, Read, Edit, Write, Grep, Glob, Agent, WebFetch

GitHub Issue Workflow

Fetch a GitHub issue, create branch, implement following TDD, and open a PR.

Arguments

$ARGUMENTS - Issue number (e.g., 42 or #42)

Instructions

Phase 1: Setup

Parse the issue number from $ARGUMENTS (strip # if present)

Fetch issue details:

gh issue view <number> --json title,body,labels,assignees,milestone,state

Assign yourself if unassigned:

gh issue edit <number> --add-assignee @me

Add appropriate labels if the issue doesn't have them:
- bug - Something isn't working
- enhancement - New feature or request
- documentation - Improvements or additions to documentation
Create a branch from main:

Determine prefix from labels:
- bug → fix/
- enhancement → feat/
- documentation → docs/
- Default → feat/
Branch name: <prefix><issue-number>-<slug> (slug: lowercase title, spaces → -, max 50 chars)
```
git checkout main && git pull
git checkout -b <branch-name>
```

Phase 2: Plan

Analyze the issue: requirements, labels, referenced issues, affected areas
Explore the codebase for context:
- Find related code in src/
- Find related tests in tests/
- Study existing patterns
Create implementation plan:
- Acceptance Criteria
- Test Strategy (which tests to write first)
- Files to Change
- Implementation Order (smallest first step)
Use EnterPlanMode if implementation is non-trivial

Phase 3: Implement

Follow strict TDD workflow (see @.claude/rules/tdd-workflow.md):

For each test:
- RED - Write failing test, verify it fails for the RIGHT reason
- GREEN - Minimal code to pass
- REFACTOR - Improve while keeping tests green

Run full test suite frequently:

./bashunit tests/
./bashunit --parallel tests/

Quality checks after each refactor:
```
make sa && make lint && shfmt -w .
```

Phase 4: Ship

Final verification:

./bashunit tests/ && ./bashunit --parallel tests/ && make sa && make lint

Commit using conventional commits with Closes #<issue-number>
Create PR using the /pr skill:
```
/pr #<issue-number>
```

Output Format

After fetching, present:

## Issue #<number>: <title>

**Labels:** <labels>
**State:** <state>
**Branch:** <branch-name>

### Description
<body content>

### Next Steps
1. Explore codebase for context
2. Create implementation plan
3. Begin TDD cycle

Plus depuis ce dépôt

même dépôt

review

TypedDevs/bashunit

Review a GitHub pull request; defaults to the current branch's PR when no number is given

2026-07-14419

TypedDevs/bashunit

Push branch and create a GitHub PR with concise, issue-linked description

2026-07-10419

release

TypedDevs/bashunit

Run pre-release validation and execute the release process

2026-06-16419

gh-issues

TypedDevs/bashunit

Walk over all open GitHub issues that are unassigned or assigned to the current user, and process each one via the /gh-issue skill, sequentially.

2026-06-03419

add-assertion

TypedDevs/bashunit

Add new assertion function with comprehensive tests following TDD

2026-03-14419

check-coverage

TypedDevs/bashunit

Analyze test coverage and identify untested code paths

2026-03-14419

GitHub Issue Workflow

Fetch a GitHub issue, create branch, implement following TDD, and open a PR.

Arguments

$ARGUMENTS - Issue number (e.g., 42 or #42)

Instructions

Phase 1: Setup

Parse the issue number from $ARGUMENTS (strip # if present)

Fetch issue details:

gh issue view <number> --json title,body,labels,assignees,milestone,state

Assign yourself if unassigned:

gh issue edit <number> --add-assignee @me

Add appropriate labels if the issue doesn't have them:

bug - Something isn't working
enhancement - New feature or request
documentation - Improvements or additions to documentation

Create a branch from main:

Determine prefix from labels:

bug → fix/
enhancement → feat/
documentation → docs/
Default → feat/

Branch name: <prefix><issue-number>-<slug> (slug: lowercase title, spaces → -, max 50 chars)

git checkout main && git pull
git checkout -b <branch-name>

Phase 2: Plan

Analyze the issue: requirements, labels, referenced issues, affected areas

Explore the codebase for context:

Find related code in src/
Find related tests in tests/
Study existing patterns

Create implementation plan:

Acceptance Criteria
Test Strategy (which tests to write first)
Files to Change
Implementation Order (smallest first step)

Use EnterPlanMode if implementation is non-trivial

Phase 3: Implement

Follow strict TDD workflow (see @.claude/rules/tdd-workflow.md):

For each test:

RED - Write failing test, verify it fails for the RIGHT reason
GREEN - Minimal code to pass
REFACTOR - Improve while keeping tests green

Run full test suite frequently:

./bashunit tests/
./bashunit --parallel tests/

Quality checks after each refactor:

make sa && make lint && shfmt -w .

Phase 4: Ship

Final verification:

./bashunit tests/ && ./bashunit --parallel tests/ && make sa && make lint

Commit using conventional commits with Closes #<issue-number>

Create PR using the /pr skill:

/pr #<issue-number>

Output Format

After fetching, present:

## Issue #<number>: <title> **Labels:** <labels> **State:** <state> **Branch:** <branch-name> ### Description <body content> ### Next Steps 1. Explore codebase for context 2. Create implementation plan 3. Begin TDD cycle