speckit-gh

Drives a GitHub issue through the full speckit pipeline to a merged pull request.

Updated Jan 28, 2026
One-click install
npx skills add https://github.com/alkampfergit/cisharpai --skill speckit-gh-alkampfergit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-gh
Source: https://github.com/alkampfergit/cisharpai/tree/main/.claude/skills/speckit-gh
Command: npx skills add https://github.com/alkampfergit/cisharpai --skill speckit-gh-alkampfergit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Manually coordinating specification, planning, implementation, and review of a GitHub issue across many tools and chat prompts is error-prone and loses context. This Skill automates the entire lifecycle of a single GitHub issue using the gh CLI, keeping every decision and approval on the issue or PR thread instead of the console. ## Core Features & Use Cases - End-to-end issue pipeline: Sequences the speckit phases (specify, clarify, plan, tasks, implement, test) from claiming an issue through opening a draft PR, watching CI, and handling reviewer comments until merge. - Human-in-the-loop approval gates: Posts every artefact (spec, plan, tasks) as a marked comment on the issue and polls for owner approval before proceeding, never auto-answering clarification questions. - Strict communication protocol: Enforces owner-login filtering, watermark-based polling, and re-fetch-before-post rules so no owner feedback is ever missed. - Use Case: Tell the agent "implement issue #42 with speckit" and it claims the issue, drafts and gets approval for the spec, plan, and tasks, opens a draft PR, implements and tests the code, watches CI, and responds to reviewer comments until the owner directs a merge. ## Quick Start Ask the agent to implement a specific GitHub issue end-to-end with speckit, for example by saying "implement issue #123 with speckit" or pasting the issue URL.

Frequently Asked Questions about speckit-gh

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

FAQPage Schema
How do I implement a GitHub issue end-to-end with speckit?▼

Invoke the skill with an issue reference such as "implement issue #123 with speckit" or a full issue URL. It claims the issue, runs the specify, clarify, plan, tasks, and implement phases, opens a draft PR, and manages CI and reviewer feedback until merge.

How does speckit-gh handle approvals and user questions?▼

All communication happens on the GitHub issue or PR thread, never the console. Each artefact is posted as a marked comment and the skill polls for a reply from the repository owner, filtering every response by the owner login resolved via gh repo view.

What are the prerequisites for running speckit-gh on a repository?▼

The gh CLI must be authenticated, the working tree must be clean on the base branch, and the .specify directory must be initialised with the spec, plan, tasks, and pr-report templates. The issue must be open, unassigned or assigned to you, and have no existing PR closing it.

Does speckit-gh merge or release pull requests automatically?▼

No. It never auto-merges, auto-closes, tags, or releases. Merging only happens after an explicit owner directive on the PR thread, and tagging or releases are left to the separate manual gitflow release process.

What happens when a speckit-gh approval poll times out?▼

If a single approval poll exceeds the approval-timeout-minutes limit (default 60), the skill parks the issue by applying the fail-label, posts a speckit:failure comment explaining the timeout, and exits without pretending success.

When should I use speckit-full instead of speckit-gh?▼

Use speckit-gh to drive one specific issue end-to-end. For label-driven polling that picks up and processes many issues across a repository automatically, use the speckit-full skill instead.