managing-relationships
Manage GitHub issue hierarchies
Creating issue hierarchies and tracking dependencies is complex with the standard GitHub CLI. This skill provides direct access to GitHub GraphQL API for managing parent-child relationships, blocking dependencies, and tracking links between issues.
下載技能 ZIP
在 Claude 中上傳
前往 設定 → 功能 → 技能 → 上傳技能
開啟並開始使用
測試它
正在使用「managing-relationships」。 Add issue #68 as a sub-issue of #67 and show the relationship
預期結果:
- Added #68 as sub-issue of #67
- Parent: Implement user authentication
- Child: Add login API endpoint
- Issue #67: Implement user authentication
- Progress: 1/3 (33%)
- Sub-issues (1):
- #68: Add login API endpoint
正在使用「managing-relationships」。 Show all relationships for issue #45
預期結果:
- ○ Issue #45: Design API endpoints
- ========================================================
- Parent: #40 - Q1 Backend Architecture
- Sub-issues (2/4):
- ○ #41: Design user endpoint
- ○ #42: Design product endpoint
- Blocked by:
- ○ #30 - Database schema approval
- Blocking:
- ○ #50 - API documentation
正在使用「managing-relationships」。 What is issue #78 blocked by and what is it blocking
預期結果:
- Dependencies for #78: Implement caching layer
- ========================================================
- Blocked by (2):
- ○ #65 - Redis setup
- ○ #70 - Cache invalidation strategy
- Blocking (1):
- ○ #85 - Performance testing
安全審計
低風險This is a legitimate GitHub automation skill that manages issue relationships using the official GitHub GraphQL API. The Python script is a straightforward CLI wrapper around `gh` CLI commands. All static findings are false positives triggered by false pattern matching on GraphQL API field names and documentation code blocks. No malicious code, data exfiltration, or harmful patterns exist.
風險因素
品質評分
你能建構什麼
Track epic progress
Create parent issues as epics and link child tasks to see overall completion percentage.
Manage feature branches
Link related issues for a feature to understand dependencies and track development progress.
Track blocking bugs
Identify which issues are blocked by others and understand test dependency chains.
試試這些提示
Create a parent issue #67 and add issues #68, #69, and #70 as sub-issues.
Show all relationships for issue #45 including parent, sub-issues, and blocking dependencies.
What issues is #78 blocked by? What issues is #78 blocking?
Create a hierarchy where #1 is epic, #2 and #3 are features under it, and #5, #6 are tasks under #2.
最佳實務
- Create all issues first, then establish relationships to avoid orphaning issues.
- Verify relationships after creation to confirm the GraphQL mutation succeeded.
- Keep hierarchies shallow (2-3 levels) for easier navigation and management.
避免
- Using task lists (- [ ] #68) instead of sub-issues API, which only creates tracking links.
- Attempting to add an issue to a new parent without checking if it already has one.
- Creating circular references in hierarchies, which GitHub will reject.