resolve-follow-ups

Resolve recorded repository follow-ups through isolated workers into verified pull requests.

Updated Sep 17, 2026
One-click install
npx skills add https://github.com/hkw2028/toy-project --skill resolve-follow-ups-hkw2028
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: resolve-follow-ups
Source: https://github.com/hkw2028/toy-project/tree/main/.agents/skills/resolve-follow-ups
Command: npx skills add https://github.com/hkw2028/toy-project --skill resolve-follow-ups-hkw2028

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Recorded follow-ups in docs/follow-ups often sit unresolved or get fixed sloppily without reproduction evidence. This Skill turns a bounded backlog of evidence-backed follow-ups into independently verified, ready-for-review pull requests while preserving items that cannot be reproduced or lack authority to fix. ## Core Features & Use Cases - Bounded backlog sweeps: Lists valid follow-ups from the fetched remote default branch, reports invalid files, and starts at most three isolated workers per sweep. - Isolated worker execution: Runs each item in its own claimed worktree and branch via Claude Routine subagents or Codex Scheduled tasks, with atomic attempt claims preventing duplicate work. - Evidence-gated resolution: Requires reproduction before editing, derives intended behavior from existing tests and specs, and returns terminal outcomes (pull-request, not-reproduced, needs-shaping, blocked) without auto-merging. - Use Case: A team accumulates docs/follow-ups entries from prior sessions. Run a sweep so each reproducible item becomes its own reviewed PR, while items needing product decisions are flagged for a later shaping session. ## Quick Start Ask the agent to sweep the repository's docs/follow-ups directory and resolve each reproducible item in an isolated worktree as a separate ready-for-review pull request.

Frequently Asked Questions about resolve-follow-ups

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I resolve recorded follow-ups into separate pull requests?

Run a sweep over docs/follow-ups so each valid item is claimed atomically, reproduced in its own worktree and branch, fixed with regression checks, and published as one ready-for-review pull request per item. Nothing is merged automatically.

What happens when a follow-up symptom cannot be reproduced?

The worker stops before any speculative source change, returns a not-reproduced outcome with the attempts made and the next useful evidence, and preserves the follow-up file. The recorded attempt suppresses duplicate retries until the content or base changes.

Can this run in Claude Code or Codex scheduled automation?

Yes. Claude Routine uses worktree-isolated subagents when creation-time base verification is available, otherwise a prepared checkout with a headless worker. Codex Scheduled tasks act as coordinators that prepare a separate verified worktree per item and launch codex exec workers.

When does a follow-up get returned as needs-shaping instead of fixed?

When the symptom reproduces but the intended behavior is not settled by existing tests, specs, or decision contracts, the worker makes no patch and returns needs-shaping. It names the unresolved product decision so a later shaping session can settle it.

Why does the sweep refuse to use the local HEAD as a base?

Workers must verify against the fetched remote default branch so fixes target current shared state. If the fetch fails, the attempt is reported as blocked before any edit rather than falling back to a stale local checkout.