autospec-run

Automates GitHub issue queues into merged code changes with traceable specs and PR outcomes.

3|1|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/berlinguyinca/autospec --skill autospec-run
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: autospec-run
Source: https://github.com/berlinguyinca/autospec/tree/main/skills/autospec-run
Command: npx skills add https://github.com/berlinguyinca/autospec --skill autospec-run

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, jq, git, curl, ollama, and includes scripts (resource) components.

What problem does it solve?

Autospec-run turns a pre-built GitHub issue implementation queue into shipped, reviewable, explainable code changes without requiring the operator to micromanage every PR.

Core Features & Use Cases

  • Autonomous monitor (Phase 4): Claims ready auto-implement issues, runs the implement→test→PR→self-review→admin-squash-merge loop, then immediately continues as new merges unblock the queue.
  • Quality and safety gates (Phases 4–6): Enforces dependency closure, path conflict avoidance, doc drift checks, rebase-and-retest before merge, and ends with a consolidated completion report.
  • Distributed queue coordination: Supports multi-machine workers via GitHub labels plus a run-state comment/heartbeat mechanism to coordinate claims safely.
  • Model-fit filtering: Optionally filters candidate issues by ctx:* and reasoning:* ceilings using ~/.autospec/model-profiles.yml and reports deferred items at run end.

Quick Start

Run autospec-run on your repo’s populated queue with the command: /autospec-run --profile claude-sonnet-cloud

Frequently Asked Questions about autospec-run

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

FAQPage Schema
How do I autonomously implement and merge GitHub issues from a queue?

You can autonomously implement and merge queued GitHub issues by running a monitor loop that claims ready issues, runs implementation, testing, PR creation, self-review, and admin squash-merge. This requires a populated auto-implement issue queue and path conflict checks before claiming.

How does autonomous code review and issue triage work with CI gates?

Autonomous code review and issue triage with CI gates works by enforcing dependency closure, rebase-and-retest before merge, and doc drift checks. The system claims issues only when dependencies are closed and path conflicts are clear, then performs admin squash-merge to finalize changes.

Can I run autonomous implementation across multiple machines for distributed queue coordination?

Yes, you can run autonomous implementation across multiple machines using distributed queue coordination. This uses GitHub labels and a run-state comment/heartbeat mechanism to safely coordinate claims between workers, preventing conflicts during the implement and merge loop.

Do I need ollama and gh to run autonomous implementation on a GitHub issue queue?

Yes, you need gh, jq, git, curl, and ollama installed to run autonomous implementation. These tools support the CLI operations, JSON parsing, repository interactions, and local model profile filtering required to process the auto-implement queue.

What is model profile filtering for autonomous issue implementation?

Model profile filtering for autonomous issue implementation is an optional mechanism that filters candidate issues by `ctx:*` and `reasoning:*` ceilings using a configuration file. It ensures tasks match your model's capabilities and reports deferred items at the end of the run.

How do I run autonomous implementation with Claude Code or Codex CLI harnesses?

You run autonomous implementation with Claude Code, OpenCode, or Codex CLI by passing a profile flag to the execution command. The system applies the implementation portion of the workflow across these multiple harnesses, monitoring phases 4–6 with autonomous merges.