Skip to content

[Extension]: Add ghp #5441

Backlog
Backlog

Description

@praveenlavu

Extension ID

ghp

Extension Name

Spec Kit for GitHub Projects - human-gated lifecycle

Version

0.1.2

Description

GitHub issue to Done through Spec Kit, with a human sign-off before every write.

Author

praveenlavu

Repository URL

https://github.com/praveenlavu/spec-kit-ghp

Download URL

https://github.com/praveenlavu/spec-kit-ghp/releases/download/v0.1.2/spec-kit-ghp-extension-0.1.2.zip

License

MIT

Homepage (optional)

https://github.com/praveenlavu/spec-kit-ghp

Documentation URL (optional)

https://github.com/praveenlavu/spec-kit-ghp/blob/main/README.md

Changelog URL (optional)

https://github.com/praveenlavu/spec-kit-ghp/blob/v0.1.2/CHANGELOG.md

Required Spec Kit Version

=1.2.1

Required Tools (optional)

- ghp (>=0.1.2) - required; the command-line program from this repository: pipx install git+https://github.com/praveenlavu/spec-kit-ghp@v0.1.2
- git - required
- gh - required; every GitHub call goes through the GitHub CLI, signed in with the project scope

Number of Commands

13

Number of Hooks (optional)

2

Tags

github-projects, issue-tracking, hitl, workflow, governance

Key Features

  • GitHub Issues and user-owned GitHub Projects only; organisation Projects are refused
  • Pulls a story issue into a per-story checklist file with its acceptance criteria copied word for word
  • Turns tasks.md into sub-issues on the story and cards on the Project; a dry run unless --apply is given
  • Every GitHub write is a preview, a person's yes, then an apply of exactly the previewed plan; a changed plan is refused
  • A check before review that every acceptance criterion has a named test, plus an optional strict mode that re-runs the approved test command
  • Opens the pull request with "Closes #N" and closes the story after the merge, each after an explicit yes
  • Optional approvals by issue comment from approvers listed on the target branch; the agent's own comments never count
  • ghp doctor and ghp status: setup health and the next step for a story
  • Optional ghp-lifecycle workflow (filed separately) with a gate before every GitHub write
  • Standard library only; ghp never reads a token (gh signs in)

Testing Checklist

  • Extension installs successfully via download URL
  • All commands execute without errors
  • Documentation is complete and accurate
  • No security vulnerabilities identified
  • Tested on at least one real project

Submission Requirements

  • Valid extension.yml manifest included
  • README.md with installation and usage instructions
  • LICENSE file included
  • GitHub release created with version tag
  • All command files exist and are properly formatted
  • Extension ID follows naming conventions (lowercase-with-hyphens)

Testing Details

Tested on:

  • macOS (Darwin 27.2.0), with Spec Kit 1.2.1 (the minimum) and Spec Kit 1.4.0 (the newest release that day)

Test project: a new empty folder where specify init ran, for each Spec Kit version; the live scenarios ran against a private and a public test repository, a public consumer test repository, and a test Project owned by a user account

Test scenarios:

  1. Installed the ghp program from the v0.1.2 tag with pip in a virtual environment (ghp --version printed 0.1.2); the uv and pipx commands were not run for 0.1.2
  2. (0.1.2) Installed the extension from the download URL on both Spec Kit versions, and again by a pinned install from the catalog and through the bundle: all exit 0, the extension file matches the checksum in the catalog entry
  3. Ran the ghp-lifecycle workflow on Spec Kit 1.4.0 on a test story, from the pull to an open pull request, then ghp done after the merge, with every GitHub write previewed, approved at a gate, then applied (terminal mode); the gate answers were typed by an AI agent that had read each preview
  4. Ran ghp push with a plan that had gone stale and saw it refuse to write; on Spec Kit 1.2.1 ran the workflow up to the push approval, with a reject at the first gate and a stale plan at the push gate
  5. In comment mode on a public test repository, with the Actions bot as the agent: ghp done closed a story from an approval comment after ghp approvals check, and an edited, rejected, stale or same-account approval was refused
  6. Ran the live test suite against GitHub on 0.1.1: 48 passed; ran the offline test suite in the 0.1.2 export: 7308 passed, 120 skipped (two tests that need a real terminal were run in the foreground, because a background run ignores Ctrl-C)
  7. (0.1.2) Started two ghp push --apply of the same story at the same instant on one machine: one made the 3 tasks, the other waited about 22 seconds, found them and wrote nothing; the story has 3 sub-issues (on 0.1.1 the same test made 6)

NOT TICKED: "All commands execute without errors". The lifecycle workflow and the Claude Code slash commands were run end to end, but every one of the 13 commands was not run on its own on each Spec Kit version. The checks that the offline tests, the live suite and the live runs did not cover are listed in the repository's docs/trust-and-limits.md ("Unverified in live runs"). The security box is a self-attestation (a secret scan of the full history, adversarial reviews, a refusal-before-write live test set), not an independent audit.

Example Usage

# Install the program and the extension
pipx install git+https://github.com/praveenlavu/spec-kit-ghp@v0.1.2
specify extension add ghp --from https://github.com/praveenlavu/spec-kit-ghp/releases/download/v0.1.2/spec-kit-ghp-extension-0.1.2.zip

# Connect, then pull a story
ghp setup
/speckit.ghp.pull 42

Proposed Catalog Entry

{
  "ghp": {
    "id": "ghp",
    "name": "Spec Kit for GitHub Projects - human-gated lifecycle",
    "description": "GitHub issue to Done through Spec Kit, with a human sign-off before every write.",
    "author": "praveenlavu",
    "version": "0.1.2",
    "download_url": "https://github.com/praveenlavu/spec-kit-ghp/releases/download/v0.1.2/spec-kit-ghp-extension-0.1.2.zip",
    "sha256": "21dc228f99fbf9b8768b6f75e889be2bb99c68ed9b5237951276e33e9dedfbda",
    "repository": "https://github.com/praveenlavu/spec-kit-ghp",
    "homepage": "https://github.com/praveenlavu/spec-kit-ghp",
    "documentation": "https://github.com/praveenlavu/spec-kit-ghp/blob/main/README.md",
    "changelog": "https://github.com/praveenlavu/spec-kit-ghp/blob/v0.1.2/CHANGELOG.md",
    "license": "MIT",
    "requires": {
      "speckit_version": ">=1.2.1",
      "tools": [
        {
          "name": "ghp",
          "version": ">=0.1.2",
          "required": true
        },
        {
          "name": "git",
          "required": true
        },
        {
          "name": "gh",
          "required": true
        }
      ]
    },
    "provides": {
      "commands": 13,
      "hooks": 2
    },
    "tags": [
      "github-projects",
      "issue-tracking",
      "hitl",
      "workflow",
      "governance"
    ],
    "verified": false,
    "created_at": "2026-11-15T00:00:00Z",
    "updated_at": "2026-11-15T00:00:00Z"
  }
}

Additional Context

  • ghp needs Python 3.9 or later; the manifest cannot say so.
  • It is not affiliated with GitHub, Microsoft or the Spec Kit project.
  • Not yet checked on real GitHub: the list in docs/trust-and-limits.md, "Unverified in live runs".
  • The ghp program (Python standard library only) is in the same repository at the same tag. A bundle and a workflow are filed alongside; the workflow as a pull request.
  • AI disclosure: this submission text was drafted with Claude Code (Claude Sonnet 5.5) in interactive, human-supervised mode, on behalf of the submitter, who authorised filing it.

Activity

  1. github-actions commented on Nov 16, 2026

    @github-actions
    Contributor

    cc @github/spec-kit-maintainers — new catalog submission for review.

  2. github-actions commented on Nov 16, 2026

    @github-actions
    Contributor

    Thanks for the submission — validation ran successfully, but one required check failed:

    • Testing Checklist not fully checked: All commands execute without errors is unchecked in the Testing Checklist section.

    To proceed, please update the issue so all required Testing Checklist and Submission Requirements checkboxes are checked (or submit a new corrected extension-submission issue). After that, maintainers can rerun validation.

    Workflow run

    Generated by 🧩 Add Community Extension from Issue Submission for #5441 · copilot · gpt53codex · 15.1 AIC · ⌖ 0.645 AIC · ⊞ 28.5K · ◷

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions