gh issues

Engineering Community

Skill notes

Phase 1 — Parse Arguments

Parse the arguments string provided after /gh-issues. Positional: owner/repo — optional. This is the source repo to fetch issues from. If omitted, detect from the current git remote: git remote get-url origin Extract owner/repo from the URL (handles both HTTPS and SSH formats).

Phase 2 — Fetch Issues

Token Resolution: First, ensure GH_TOKEN is available. Check environment: If empty, read from config: If still empty, check /data/.clawdbot/openclaw.json: Export as GH_TOKEN for subsequent commands:

Phase 3 — Present & Confirm

Display a markdown table of fetched issues: · Title · Labels 42 · Fix null pointer in parser · bug, critical 37 · Add retry logic for API calls · enhancement If FORK_MODE is active, also display:

Phase 4 — Pre-flight Checks

Run these checks sequentially via exec: Dirty working tree check: If output is non-empty, warn the user: "Working tree has uncommitted changes. Sub-agents will create branches from HEAD — uncommitted changes will NOT be included. Continue?" Wait for confirmation. If declined, stop.

Phase 5 — Spawn Sub-agents (Parallel)

Cron mode (--cron is active): Sequential cursor tracking: Use a cursor file to track which issue to process next: Read the cursor file (create if missing): last_processed: issue number of the last completed issue (or null if none) in_progress: issue number currently being processed (or null)

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
94 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@cohen-liel · Apache-2.0
Token usage
Heavy
Setup complexity
Manual integration
External API key
Required · GitHub
Operating systems
macOS · Linux · Windows
Runtime requirements
Node.js
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
  • Env read
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview gh-issues.preview
# Step 6.6 — Review Results

| PR | Comments Addressed | Comments Skipped | Commit | Status |
|----|-------------------|-----------------|--------|--------|
| #99 fix/issue-42 | 3 | 0 | abc123f | All addressed |
| #101 fix/issue-37 | 1 | 1 | def456a | 1 needs manual review |

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.