gh 代码验证
- 作者仓库星标 330
- 许可证 MIT
- 作者仓库 claude-skill-registry
Create GitHub Issue
Create a new GitHub issue for the gittower/git-flow-next repository following project guidelines.
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 issue
- If
Check for Duplicates
- Search existing issues for similar topics
- If potential duplicates found, show them to the user and ask to confirm creation
Determine Issue Type and Labels
bug- Something isn't workingenhancement- Improvement to existing featurefeature- New feature requestdocumentation- Documentation improvements
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
## 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
## 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>
- Report Result
- Show the created issue URL
- Suggest next step:
/analyze-issue <number>to start working on it
- 流狐分类
- 数据
- 作者声明 Agent
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 94 / 100 · 启发式扫描,不代表运行安全
- 作者 / 版本 / 许可
- @majiayu000 · MIT
- 流狐 Token 估算
- 低消耗
- 流狐接入估算
- 即装即用
- 是否需要外部 API Key
- 未发现要求
- 检测到的系统要求
- 未声明
- 底层运行要求
- 未声明
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 检测到的网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
档案由构建时根据 SKILL.md 与安装命令自动衍生,可能与作者实际意图存在差异。
需要注意: 未限定 allowed-tools,默认拥有全部工具权限。
作者没有在当前 SKILL.md 中定义固定输出样例。 Instructions
Gather Information If $ARGUMENTS is provided, use it as the issue title/description If no arguments, ask the user for:
Issue Body Templates
Issue Body Templates
Bug Report
Bug Report
Description
<Clear description of the bug>
Steps to Reproduce
1. 2. 3.
Expected Behavior
<What should happen>
# 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 证据边界与执行链路
作者原文负责流程事实;流狐只索引当前章节、要点、文件与命令。
章节 -> Instructions → Issue Body Templates → Bug Report → Description → Steps to Reproduce → Expected Behavior
要点 -> Gather Information · Check for Duplicates · Determine Issue Type and Labels · Create the Issue · Report Result
文件/命令 -> $ARGUMENTS · bug · enhancement · feature · documentation · /analyze-issue <number>
内容 SHA-256 -> b66bc71925b4
方法与流程
适用与边界
原文中的明确线索
$ARGUMENTS、bug、enhancement、feature、documentation、/analyze-issue <number>