Menú
Sweep the GitHub issue queue and deliver one reviewable PR per labeled issue. Use when running the autonomous issue pipeline's self-firing sweep (scheduled or on demand), or when asked to process issues labeled `llm-github-issue`.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
| name | gh-process-issues |
| description | Sweep the GitHub issue queue and deliver one reviewable PR per labeled issue. Use when running the autonomous issue pipeline's self-firing sweep (scheduled or on demand), or when asked to process issues labeled `llm-github-issue`. |
The issue-tracker half of Manifold's self-firing agents (design: docs/llm-github-issues.md).
A human curates the queue by labeling an issue llm-github-issue; everything after the
label is autonomous. The label fires the work; the human only answers questions in the
thread and merges the PR. There is no chat to ask in — the conversation lives in the
issue thread, so the pipeline runs with no interactive prompts: every ambiguity resolves
to either a documented assumption or a feedback-needed stop.
gh, no memory of past runs)| State | How to read it | Move |
|---|---|---|
| Queued | open + llm-github-issue, no feedback-needed, no open PR with Fixes #n | process |
| Blocked | feedback-needed present | skip — waiting on a human |
| Delivered | an open PR closes it | skip — review pending |
| Done | PR merged, issue auto-closed | leaves every query |
# The queue
gh issue list --label llm-github-issue --state open --json number,title,labels
# Per issue: blocked or already delivered?
gh issue view <n> --json labels,closedByPullRequestsReferences
gh pr list --search "Fixes #<n> in:body" --state open
Statelessness is the point — a sweep can crash, run twice, or run from another machine; the tracker holds all the state.
Fixes #a, Fixes #b); if
branches have already diverged, comment on each PR/issue declaring the merge order.issue/<n>-<slug> (an isolated worktree when running locally).verify skill). A successful repro becomes the verification baseline ("this now
passes"). A failed repro is posted to the thread as a comment (what was tried, on what)
and work continues — non-reproducibility is recorded honestly, never hidden.testing skill). Run the suite before changing anything for a
baseline, then the suite and the typecheck gates after. Re-run the reproduction and
confirm it now passes.gh-create-pr skill). One PR, Fixes #n in the body, evidence
attached: test output, the reproduction now passing, and before/after screenshots for
user-facing issues (the verify skill). Post a comment on the issue linking the PR.Two outcomes only, never a blocking question in a chat:
feedback-needed label, and stop work on that issue. A human answers in the thread
and removes the label; the next sweep resumes with the full thread as context.llm-github-issue, no processing.log.md entry — every comment, label event, and PR is
already the audit trail.CLAUDE.md / AGENTS.md; the rest are dropped.Use whenever running tests in this project — verifying a fix, validating a PR, running the suite after changes, or checking a single file. Covers which command to use, how the `better-sqlite3` ABI rebuild fits in, and how to target individual files.
Detect documentation pages whose covered code has drifted and open one doc-sync PR per stale page. Use when running the documentation wiki's self-firing lint (scheduled or on demand), or when asked to sync the architecture docs with the code.
Create GitHub issues from agent findings, bugs, regressions, UX problems, or follow-up work. Use when the user asks to create, file, or draft a GitHub issue and the result should be a structured issue body plus a `gh issue create` command.
Watch a video that Manifold has pre-staged. Manifold's main process downloads the video, extracts auto-scaled frames with ffmpeg, and produces a timestamped transcript (native captions or gpt-4o-transcribe). This skill receives the report path and tells Claude to read each frame.
Create GitHub pull requests for completed fixes or features. Use when the user asks to prepare, push, or open a PR and the result should include a meaningful remote branch name, commit, and PR title tied to the actual bug fix or main change rather than an agent or worktree name.
Manifold design system — philosophy, principles, and patterns for UI work. Use when creating or modifying UI components, styling, theming, layout, or any visual aspect of the application.