gh issue

Data Community

Skill notes

Instructions

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

Enhancement/Feature

Report Result Show the created issue URL Suggest next step: /analyze-issue <number> to start working on it

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
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.

Author source file SKILL.md

# 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

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.