生长激素问题
- 作者仓库星标 330
- 许可证 MIT
- 作者仓库 claude-skill-registry
- 领域
- 数据
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 94 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @majiayu000 · MIT
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 即装即用
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 运行环境要求
- 未检出明确要求
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
# 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
章节与文件索引
按说明文件中的顺序排列。
使用说明
增强/功能
文件/命令 -> $ARGUMENTS · bug · enhancement · feature · documentation · /analyze-issue <number>
内容校验值 -> b66bc71925b4
当前原文的自动摘译,尚未人工审校。
使用说明
收集信息 如果提供了
$ARGUMENTS,则将其用作问题标题/描述 如果没有参数,则询问用户: 问题类型(错误、增强、功能) 问题的简要描述增强/功能
报告结果 显示创建的问题 URL 建议下一步:
/analyze-issue <number>开始处理它