gh issue
- Repo stars 330
- License MIT
- Author repo claude-skill-registry
- Domain
- Data
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 94 / 100 · heuristic scan, not runtime safety proof
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- Author / version / license
- @majiayu000 · MIT
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No explicit requirements detected
- Detected file/system behavior
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
# Create GitHub Issue
Create a new GitHub issue for the gittower/git-flow-next repository following project guidelines.
## Instructions
1. **Gather Information**
- If `$ARGUMENTS` is provided, use it as the issue title/description
- If no arguments, ask the user for:
- Issue type (bug, enhancement, feature)
- Brief description of the issue
2. **Check for Duplicates**
- Search existing issues for similar topics
- If potential duplicates found, show them to the user and ask to confirm creation
3. **Determine Issue Type and Labels**
- `bug` - Something isn't working
- `enhancement` - Improvement to existing feature
- `feature` - New feature request
- `documentation` - Documentation improvements
4. **Create the Issue**
- Use clear, descriptive title (imperative mood: "Add...", "Fix...", "Update...")
- Structure the body with appropriate sections based on type
## Issue Body Templates
### Bug Report
```markdown
## Description
<Clear description of the bug>
## Steps to Reproduce
1.
2.
3.
## Expected Behavior
<What should happen>
## Actual Behavior
<What actually happens>
## Environment
- OS:
- Git version:
- git-flow-next version:
```
### Enhancement/Feature
```markdown
## Description
<Clear description of the enhancement/feature>
## Motivation
<Why is this needed? What problem does it solve?>
## Proposed Solution
<How should this work?>
## Alternatives Considered
<Other approaches considered, if any>
```
5. **Report Result**
- Show the created issue URL
- Suggest next step: `/analyze-issue <number>` to start working on it
Sections and files
Listed in source order.
sections -> Instructions → Issue Body Templates → Bug Report → Enhancement/Feature
terms -> Gather Information · Check for Duplicates · Determine Issue Type and Labels · Create the Issue · Report Result
files/cmd -> $ARGUMENTS · bug · enhancement · feature · documentation · /analyze-issue <number>
body sha256 -> b66bc71925b4
Instructions
Gather Information If
$ARGUMENTSis provided, use it as the issue title/description If no arguments, ask the user for: Issue type (bug, enhancement, feature) Brief description of the issueEnhancement/Feature
Report Result Show the created issue URL Suggest next step:
/analyze-issue <number>to start working on it