Solve issue

Skill Hsiii/human-out-of-loop/skills/solve-issue

Skills curated for Codex app for less human-in-the-loop

Install

npx -y skills add Hsiii/human-out-of-loop --skill solve-issue

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Solve GitHub issues directly through implementation and $pr publication. Use `$solve-issue #<issue>` for one exact issue in the current task, or `$solve-issue <amount>` to dispatch that many independent issue-solving tasks in parallel.

SKILL.md

2.7 KB, as published. Nobody here has run it

Select

$solve-issue #<positive-issue-number>: solve that issue in the current task; never create a worker or substitute another issue.
$solve-issue <positive-amount>: select that many distinct eligible issues in ascending order and immediately create one sidebar-visible task per issue in parallel. If fewer qualify, dispatch all remaining eligible issues and report the shortage.
$solve-issue: solve one eligible issue in the current task.

Eligible: open, with no open or draft PR covering it through a GitHub Development link or closing keyword. Ignore incidental mentions. Recheck once before dispatch.

Exact-target failure:

ISSUE_SKIPPED issue=<number> reason=<not_found|not_open>
ISSUE_SKIPPED issue=<number> reason=covered_by_pr pr=<url>

Dispatch

Keep exact and default runs in the invoking task. For amount runs, use only the selected issue tasks; do not create separate developer, reviewer, or publication tasks.
Give every issue an isolated worktree and branch named <type>/<short-kebab-description>, using the narrowest of fix, feat, docs, refactor, test, or chore. Never namespace it.
Call set_thread_title once per task and never change it:
- Exact/default task: Solve #<issue>
- Amount orchestrator: Solve <amount> issues
- Amount worker: #<issue>: <short-description>
Give each amount worker the repository, issue + URL, base, branch, absolute worktree, and optional media path. The orchestrator only dispatches, waits, reports terminal results, and resumes existing workers without duplicating them.

Solve

Each issue-owning task completes the whole workflow:

Activate $ponytail at full intensity.
Implement the issue, run relevant checks, and commit the complete solution.
For UI changes, keep .codex-pr-media/ untracked through .git/info/exclude and capture matched, reproducible before/after media: video for interaction, motion, or multiple steps; images otherwise.
Require a clean worktree except ignored PR media, then run $pr.
If $pr finds actionable problems, fix and commit them, rerun checks, and invoke $pr again. Repeat in the same task until it publishes a draft PR or local package.
Report the issue, published head, PR URL or absolute draft path, and checks. Never merge or mark a PR ready.

On continuation, find and resume the existing issue-owning task, branch, worktree, and draft. Never create replacements for work that still exists.