تشغيل أي مهارة في Manus بنقرة واحدة

ابدأ الآن

gh-issue

النجوم١٨

التفرعات٠

آخر تحديث٣ مايو ٢٠٢٦ في ١٨:٥٦

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

التثبيت

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

تشغيل في Manus

المصدر

Chemaclass

Chemaclass/bashdep

فتح مستودع GitHub عرض مستودعات المنشئ

تنزيل

تشغيل في Manus

المهن ذات الصلةSOC

استنادا إلى تصنيف SOC المهني

مطوّرو البرمجياتمهن الحاسوب والرياضيات·SOC 15-1252

SKILL.md

readonly

name	gh-issue
description	Fetch a GitHub issue, create a branch, plan and implement with TDD, then open a 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 a 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

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 (which bashdep:: function or doc).
Explore the codebase for context:
- Find the relevant section in bashdep (single file)
- Find the closest related tests in tests/unit/bashdep_test.sh
- Read the corresponding entry in docs/api.md or docs/behavior.md
Create implementation plan:
- Acceptance Criteria
- Test Strategy (which tests to write first — pure-logic vs filesystem vs snapshot)
- Files to Change (bashdep, tests/unit/bashdep_test.sh, docs/*.md, CHANGELOG.md)
- 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 in bashdep to pass
- REFACTOR — Improve while keeping tests green
Run the suite frequently:
```
make test
```
Quality checks after each refactor:
```
make sa && make lint
```
Mode coverage — if the change is mutating, add tests for BASHDEP_DRY_RUN, BASHDEP_SILENT, BASHDEP_VERBOSE, BASHDEP_FORCE as relevant.

Phase 4: Ship

Final verification:
```
make pre_commit/run
```
Commit using the /commit skill, with a body referencing the issue (e.g., 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 `bashdep` for the relevant function
2. Create implementation plan
3. Begin TDD cycle

المزيد من هذا المستودع

نفس المستودع

add-command

Chemaclass/bashdep

Add a new bashdep:: lifecycle command with TDD

2026-05-0318

commit

Chemaclass/bashdep

Stage and commit changes using conventional commits format

2026-05-0318

doctor-check

Chemaclass/bashdep

Coverage gap analysis for the bashdep public API plus a bashdep::doctor audit

2026-05-0318

fix-test

Chemaclass/bashdep

Debug and fix failing bashdep tests systematically

2026-05-0318

Chemaclass/bashdep

Push branch and create a GitHub PR following the bashdep PR template

2026-05-0318

pre-release

Chemaclass/bashdep

Run a comprehensive pre-release validation checklist for bashdep

2026-05-0318

GitHub Issue Workflow

Fetch a GitHub issue, create a 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

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 (which bashdep:: function or doc).

Explore the codebase for context:

Find the relevant section in bashdep (single file)
Find the closest related tests in tests/unit/bashdep_test.sh
Read the corresponding entry in docs/api.md or docs/behavior.md

Create implementation plan:

Acceptance Criteria
Test Strategy (which tests to write first — pure-logic vs filesystem vs snapshot)
Files to Change (bashdep, tests/unit/bashdep_test.sh, docs/*.md, CHANGELOG.md)
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 in bashdep to pass
REFACTOR — Improve while keeping tests green

Run the suite frequently:

make test

Quality checks after each refactor:

make sa && make lint

Mode coverage — if the change is mutating, add tests for BASHDEP_DRY_RUN, BASHDEP_SILENT, BASHDEP_VERBOSE, BASHDEP_FORCE as relevant.

Phase 4: Ship

Final verification:

make pre_commit/run

Commit using the /commit skill, with a body referencing the issue (e.g., 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 `bashdep` for the relevant function 2. Create implementation plan 3. Begin TDD cycle