GitHub 问题管理工具 - 支持模板、元数据与智能上下文检测

Issue Management by constellos/claude-code-plugins

5 GitHub Stars

GitHub

安装命令

npx skills add https://github.com/constellos/claude-code-plugins --skill 'Issue Management'

开发项目管理自动化

🇨🇳中文介绍

问题管理

提供全面的 GitHub 问题生命周期管理，包含模板、元数据和智能上下文检测功能。

目的

问题管理功能提供对 GitHub 问题操作的显式控制。虽然钩子（hooks）会在首次提示时自动创建问题，但此技能允许用户直接管理问题的创建、更新、标签分配、指派和关联，并完全控制模板和元数据。

使用场景

使用特定模板（bug/feature/epic/task）创建问题
更新现有问题的元数据（标签、指派人、里程碑）
将问题关联为父子关系或相关关系
搜索和筛选问题
当钩子不适合工作流程时（例如，一次性创建多个问题）

核心功能

问题创建

使用结构化模板创建问题：

# 使用模板创建 Bug 报告
gh issue create --title "Auth fails on Safari" --body "$(cat <<'EOF'
## Bug Description

Authentication fails silently on Safari 17.2

## Steps to Reproduce

1. Open Safari 17.2
2. Navigate to /login
3. Enter credentials
4. Click Sign In

## Expected Behavior

User should be redirected to dashboard

## Actual Behavior

Page reloads with no error message

## Environment

- OS: macOS 14.2
- Browser: Safari 17.2
- Version: v1.5.0
EOF
)"

可用模板：

getBugTemplate() - 包含复现步骤的 Bug 报告模板
getFeatureTemplate() - 包含问题陈述的功能请求模板

广告位招租

在这里展示您的产品或服务

触达数万 AI 开发者，精准高效

联系我们

钩子	自动行为	使用技能的时机
create-issue-on-prompt	在首次提示时创建问题	创建多个问题，使用特定模板
sync-plan-to-issue	将计划文件同步到问题	根据计划变更手动更新问题

示例 1：使用模板创建 Bug

# 使用 getBugTemplate() 和 renderTemplate()
TEMPLATE=$(cat <<'EOF'
## Bug Description

{{description}}

## Steps to Reproduce

1. {{step1}}
2. {{step2}}
3. {{step3}}

## Expected Behavior

{{expected}}

## Actual Behavior

{{actual}}

## Environment

- OS: {{os}}
- Browser: {{browser}}
- Version: {{version}}
EOF
)

# 替换变量并创建问题
gh issue create \
  --title "Safari auth failure" \
  --label "bug,priority:high" \
  --body "$TEMPLATE" # (变量替换后)

示例 2：创建史诗问题

# 创建包含任务清单的史诗问题
PARENT=$(gh issue create \
  --title "Implement authentication system" \
  --label "epic" \
  --body "$(cat <<'EOF'
## Epic Overview

Build complete authentication system with OAuth and email/password support.

## Goals

- OAuth integration (Google, GitHub)
- Email/password authentication
- Password reset flow
- Session management

## Success Criteria

- All auth flows tested
- Security audit passed
- Documentation complete

## Subtasks

- [ ] OAuth integration
- [ ] Email/password auth
- [ ] Password reset
- [ ] Session management
EOF
)" \
  --json number -q .number)

示例 3：根据工作类型更新问题标签

# 从标题检测工作类型
TITLE="Fix authentication bug in Safari"
WORK_TYPE="fix"  # 由 detectWorkType() 检测

# 添加适当的标签
gh issue edit 42 --add-label "bug,browser:safari,priority:high"

示例 4：将问题关联到分支

# 向问题正文添加分支引用
CURRENT_BODY=$(gh issue view 42 --json body -q .body)
UPDATED_BODY="$CURRENT_BODY

---

**Branch:** \`42-fix/safari-auth-bug\`"

echo "$UPDATED_BODY" | gh issue edit 42 --body-file -

示例 5：批量创建问题

# 创建多个相关问题
ISSUES=(
  "Implement login form:feature"
  "Add form validation:chore"
  "Create auth API endpoints:feature"
  "Write authentication tests:chore"
)

for item in "${ISSUES[@]}"; do
  TITLE="${item%:*}"
  TYPE="${item#*:}"
  LABEL=$(echo "$TYPE" | sed 's/feature/enhancement/;s/fix/bug/')

  gh issue create --title "$TITLE" --label "$LABEL" --body "Task for authentication epic"
done

使用模板 - 结构化的问题更易于理解和跟踪
检测工作类型 - 根据内容自动为问题添加标签
关联问题 - 使用父子问题和相关问题引用
更新状态文件 - 手动创建问题时保持 .claude/logs/ 文件同步
检查现有问题 - 创建前先搜索以避免重复
使用一致的标签 - 遵循项目的标签约定
添加上下文 - 包含分支名称、相关 PR 和文件引用

getBugTemplate() - Bug 报告模板
getFeatureTemplate() - 功能请求模板
getEpicTemplate(subtasks?) - 包含可选子任务的史诗模板
getTaskTemplate() - 简单任务模板
renderTemplate(template, vars) - 替换变量
getMinimalIssueBody(description, context?) - 基本正文
addBranchReference(body, branchName) - 添加分支标记

detectWorkType(prompt, issueLabels?) - 从文本中检测工作类型
formatWorkTypeLabel(workType) - 格式化为人类可读的标签

.claude/logs/plan-issues.json - 计划 → 问题映射
.claude/logs/branch-issues.json - 分支 → 问题映射

模式：从计划创建问题

# 读取计划文件
PLAN_CONTENT=$(cat .claude/plans/feature-auth.md)

# 从第一个标题中提取标题
TITLE=$(echo "$PLAN_CONTENT" | grep -m1 "^# " | sed 's/^# //')

# 使用计划内容创建问题
ISSUE_NUM=$(gh issue create \
  --title "$TITLE" \
  --label "planned" \
  --body "$PLAN_CONTENT" \
  --json number -q .number)

# 保存到状态文件
echo "{\"feature-auth\": {\"issueNumber\": $ISSUE_NUM}}" > .claude/logs/plan-issues.json

模式：与当前工作同步问题

# 获取当前分支
BRANCH=$(git rev-parse --abbrev-ref HEAD)

# 提取问题编号
ISSUE_NUM=$(echo "$BRANCH" | grep -oE '^[0-9]+')

if [ -n "$ISSUE_NUM" ]; then
  # 使用进度更新问题
  gh issue comment $ISSUE_NUM --body "🚧 Currently working on this in branch \`$BRANCH\`"
fi

模式：关闭相关问题

# 当史诗关闭时，关闭史诗中的所有问题
PARENT=42
CHILD_ISSUES=$(gh issue list --search "in:body \"Parent Issue: #$PARENT\"" --json number -q '.[].number')

for issue in $CHILD_ISSUES; do
  gh issue close $issue --comment "Closing as part of completed epic #$PARENT"
done

🇺🇸English

Issue Management

Comprehensive GitHub issue lifecycle management with templates, metadata, and intelligent context detection.

Purpose

Issue Management provides explicit control over GitHub issue operations. While hooks automatically create issues on first prompt, this skill allows users to directly manage issue creation, updates, labeling, assignment, and linking with full control over templates and metadata.

When to Use

Creating issues with specific templates (bug/feature/epic/task)
Updating existing issue metadata (labels, assignees, milestones)
Linking issues as parent-child or related
Searching and filtering issues
When hooks don't fit the workflow (e.g., creating multiple issues at once)

Core Capabilities

Issue Creation

Create issues using structured templates:

# Bug report with template
gh issue create --title "Auth fails on Safari" --body "$(cat <<'EOF'
## Bug Description

Authentication fails silently on Safari 17.2

## Steps to Reproduce

1. Open Safari 17.2
2. Navigate to /login
3. Enter credentials
4. Click Sign In

## Expected Behavior

User should be redirected to dashboard

## Actual Behavior

Page reloads with no error message

## Environment

- OS: macOS 14.2
- Browser: Safari 17.2
- Version: v1.5.0
EOF
)"

Available Templates:

getBugTemplate() - Bug report with repro steps
getFeatureTemplate() - Feature request with problem statement
getEpicTemplate() - Epic with subtasks checklist
getTaskTemplate() - Simple task with acceptance criteria

Utilities:

renderTemplate(template, vars) - Substitute {{varName}} placeholders
getMinimalIssueBody(description, context?) - Basic issue without template

Issue Updates

Update issue metadata after creation:

# Add labels
gh issue edit 42 --add-label "bug,priority:high"

# Assign users
gh issue edit 42 --add-assignee @me,@username

# Update milestone
gh issue edit 42 --milestone "v2.0"

# Update body
gh issue edit 42 --body-file updated-description.md

Issue Linking

Link issues with parent-child or related relationships:

# Parent-child (in issue body)
**Parent Issue:** #42

This issue implements the authentication flow from the parent epic.

# Related issues (in body)
**Related Issues:** #40, #41, #43

# Closes references (auto-links on merge)
Closes #42
Fixes #43

Utilities:

addBranchReference(issueBody, branchName) - Add branch marker to issue

Issue Search

Find issues with advanced queries:

# Search by label
gh issue list --label "bug"

# Search by state and assignee
gh issue list --state open --assignee @me

# Search with text query
gh issue list --search "authentication in:title,body"

# Search by milestone
gh issue list --milestone "v2.0"

# Complex search
gh issue list --search "is:open label:bug author:@me created:>2024-01-01"

Context Detection

The skill automatically detects context from:

Branch names - Extracts issue number from 42-feature/name format
State files - Checks .claude/logs/branch-issues.json for linked issues
Work type - Detects from prompt using detectWorkType() for auto-labeling
Session context - Uses current session info for metadata

Integration with Hooks

This skill complements the automatic hooks:

Hook	Automatic Behavior	When to Use Skill
create-issue-on-prompt	Creates issue on first prompt	Create multiple issues, use specific templates
sync-plan-to-issue	Syncs plan files to issues	Manually update issue from plan changes

State Files:

.claude/logs/plan-issues.json - Plan → Issue mapping
.claude/logs/branch-issues.json - Branch → Issue mapping

Work Type Detection

Automatically categorize issues:

import { detectWorkType, formatWorkTypeLabel } from '../shared/hooks/utils/work-type-detector.js';

const workType = detectWorkType('fix the authentication bug');
// Returns: 'fix'

const label = formatWorkTypeLabel(workType);
// Returns: 'Bug Fix'

Patterns:

fix - bug, error, broken, crash, fail
feature - add, create, implement, build, new
docs - document, readme, comment, explain
refactor - clean, improve, optimize, restructure
chore - maintain, update, upgrade, config

Examples

Example 1: Create Bug with Template

# Use getBugTemplate() and renderTemplate()
TEMPLATE=$(cat <<'EOF'
## Bug Description

{{description}}

## Steps to Reproduce

1. {{step1}}
2. {{step2}}
3. {{step3}}

## Expected Behavior

{{expected}}

## Actual Behavior

{{actual}}

## Environment

- OS: {{os}}
- Browser: {{browser}}
- Version: {{version}}
EOF
)

# Substitute variables and create issue
gh issue create \
  --title "Safari auth failure" \
  --label "bug,priority:high" \
  --body "$TEMPLATE" # (after variable substitution)

Example 2: Create Epic Issue

# Create epic issue with task checklist
PARENT=$(gh issue create \
  --title "Implement authentication system" \
  --label "epic" \
  --body "$(cat <<'EOF'
## Epic Overview

Build complete authentication system with OAuth and email/password support.

## Goals

- OAuth integration (Google, GitHub)
- Email/password authentication
- Password reset flow
- Session management

## Success Criteria

- All auth flows tested
- Security audit passed
- Documentation complete

## Subtasks

- [ ] OAuth integration
- [ ] Email/password auth
- [ ] Password reset
- [ ] Session management
EOF
)" \
  --json number -q .number)

Example 3: Update Issue Labels Based on Work Type

# Detect work type from title
TITLE="Fix authentication bug in Safari"
WORK_TYPE="fix"  # Detected by detectWorkType()

# Add appropriate labels
gh issue edit 42 --add-label "bug,browser:safari,priority:high"

Example 4: Link Issue to Branch

# Add branch reference to issue body
CURRENT_BODY=$(gh issue view 42 --json body -q .body)
UPDATED_BODY="$CURRENT_BODY

---

**Branch:** \`42-fix/safari-auth-bug\`"

echo "$UPDATED_BODY" | gh issue edit 42 --body-file -

Example 5: Bulk Issue Creation

# Create multiple related issues
ISSUES=(
  "Implement login form:feature"
  "Add form validation:chore"
  "Create auth API endpoints:feature"
  "Write authentication tests:chore"
)

for item in "${ISSUES[@]}"; do
  TITLE="${item%:*}"
  TYPE="${item#*:}"
  LABEL=$(echo "$TYPE" | sed 's/feature/enhancement/;s/fix/bug/')

  gh issue create --title "$TITLE" --label "$LABEL" --body "Task for authentication epic"
done

Best Practices

Use templates - Structured issues are easier to understand and track
Detect work type - Automatically label issues based on content
Link issues - Use parent-child and related issue references
Update state files - Keep .claude/logs/ files synced when creating issues manually
Check existing issues - Search before creating to avoid duplicates
Use consistent labels - Follow project's labeling conventions
Add context - Include branch names, related PRs, and file references

Utilities Reference

Templates

getBugTemplate() - Bug report template
getFeatureTemplate() - Feature request template
getEpicTemplate(subtasks?) - Epic with optional subtasks
getTaskTemplate() - Simple task template
renderTemplate(template, vars) - Substitute variables
getMinimalIssueBody(description, context?) - Basic body
addBranchReference(body, branchName) - Add branch marker

Work Type

detectWorkType(prompt, issueLabels?) - Detect work type from text
formatWorkTypeLabel(workType) - Format as human-readable label

State Files

.claude/logs/plan-issues.json - Plan → Issue mapping
.claude/logs/branch-issues.json - Branch → Issue mapping

Common Patterns

Pattern: Create Issue from Plan

# Read plan file
PLAN_CONTENT=$(cat .claude/plans/feature-auth.md)

# Extract title from first heading
TITLE=$(echo "$PLAN_CONTENT" | grep -m1 "^# " | sed 's/^# //')

# Create issue with plan content
ISSUE_NUM=$(gh issue create \
  --title "$TITLE" \
  --label "planned" \
  --body "$PLAN_CONTENT" \
  --json number -q .number)

# Save to state file
echo "{\"feature-auth\": {\"issueNumber\": $ISSUE_NUM}}" > .claude/logs/plan-issues.json

Pattern: Sync Issue with Current Work

# Get current branch
BRANCH=$(git rev-parse --abbrev-ref HEAD)

# Extract issue number
ISSUE_NUM=$(echo "$BRANCH" | grep -oE '^[0-9]+')

if [ -n "$ISSUE_NUM" ]; then
  # Update issue with progress
  gh issue comment $ISSUE_NUM --body "🚧 Currently working on this in branch \`$BRANCH\`"
fi

Pattern: Close Related Issues

# Close all issues in epic when epic closes
PARENT=42
CHILD_ISSUES=$(gh issue list --search "in:body \"Parent Issue: #$PARENT\"" --json number -q '.[].number')

for issue in $CHILD_ISSUES; do
  gh issue close $issue --comment "Closing as part of completed epic #$PARENT"
done

Weekly Installs

Repository

constellos/clau…-plugins

GitHub Stars

First Seen

Jan 1, 1970

Security Audits

Gen Agent Trust HubPass SocketPass SnykWarn

agent-browser 浏览器自动化工具 - Vercel Labs 命令行网页操作与测试

144,300 周安装