Fetch GitHub issues, spawn sub-agents to implement fixes and open PRs, then monitor and address PR review comments. Usage: /gh-issues [owner/repo] [--label bug] [--limit 5] [--milestone v1.0] [--assignee @me] [--fork user/repo] [--watch] [--interval 5] [--reviews-only] [--cron] [--dry-run] [--model glm-5] [--notify-channel -1002381931352]
72
61%
Does it follow best practices?
Impact
100%
2.00xAverage score across 3 eval scenarios
Risky
Do not use without reviewing
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/gh-issues/SKILL.mdGitHub API authentication and issue fetching
Uses curl not gh
100%
100%
Bearer token format
100%
100%
Accept header included
100%
100%
Token env check first
50%
100%
First config fallback
100%
100%
Second config fallback
100%
100%
Filters pull requests
0%
100%
401/403 error message
33%
100%
Uses issues API endpoint
100%
100%
Correct query params
100%
100%
Sub-agent issue fix workflow and PR creation
Branch name format
100%
100%
Commit message prefix
100%
100%
Commit closes issue
37%
100%
Credential helper disabled
0%
100%
Token in remote URL
60%
100%
GIT_ASKPASS=true on push
0%
100%
No gh CLI in push/PR steps
100%
100%
PR Summary section
100%
100%
PR Changes section
0%
100%
PR Testing section
100%
100%
Confidence check
0%
100%
No force-push
100%
100%
No base branch modification
0%
100%
Pre-flight deduplication and claims tracking
PR check via GitHub API
16%
100%
Branch check via GitHub API
33%
100%
Branch check on push repo
100%
100%
Claims file path
0%
100%
Claims key format
0%
100%
Claims value is ISO timestamp
0%
100%
Two-hour expiry
0%
100%
Expired claims cleaned up
62%
100%
Creates claims dir if missing
37%
100%
Uses curl with Bearer token
25%
100%
b3cef5f
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.