Skip to content

Add ghp-lifecycle to community catalog - #5443

Open
praveenlavu wants to merge 2 commits into
github:mainfrom
praveenlavu:community/add-ghp-lifecycle
Open

praveenlavu wants to merge 2 commits into
github:mainfrom
praveenlavu:community/add-ghp-lifecycle

Conversation

@praveenlavu

Copy link
Copy Markdown
Contributor

Description

Adds the ghp-lifecycle workflow to workflows/catalog.community.json (new entry, alphabetical by id) and a row to docs/community/workflows.md. A workflow-catalog change goes through a pull request; there is no workflow issue form. The matching extension and bundle are filed as issues: #5441 (extension) and #5442 (bundle).

  • Workflow ID: ghp-lifecycle Version: 0.1.2 License: MIT
  • Repository: https://github.com/praveenlavu/spec-kit-ghp (tag v0.1.2, GitHub release with spec-kit-ghp-extension-0.1.2.zip, ghp-0.1.2.zip and SHA256SUMS)
  • Pinned URL: https://github.com/raw/praveenlavu/spec-kit-ghp/v0.1.2/workflows/ghp-lifecycle/workflow.yml
  • sha256 of that file: f6bab8adfc69967681e562b80dfdb9a772d285b72f67b8b9f73de4b8428e22f2 (computed from the downloaded file, 2026-11-16)

It takes a GitHub story issue to an open pull request (spec, plan, tasks, push, implement, gate, review, PR); every GitHub write is a preview, a human gate that shows the plan, and an apply that refuses if the plan changed. It needs the ghp program (Python standard library only) and the GitHub CLI; the workflow README says so. GitHub Issues and user-owned GitHub Projects only.

Testing

  • Catalog-only change: the Spec Kit test suite was not run; the JSON parses, re-serialises byte-identically before the edit, and the workflows keys are in alphabetical order.
  • From the published v0.1.2 artifacts (2026-11-16, macOS): on Spec Kit 1.2.1 (the minimum) and 1.4.0, a clean project installed the workflow from its raw address and by a pinned catalog install, and the bundle from the release file; all exit 0. The workflow.yml hash equals the value above and the documentation and changelog URLs answer 200.
  • Workflow run end to end (terminal mode, on 0.1.1; the 0.1.2 workflow.yml differs from it by its version line only): on Spec Kit 1.4.0, a test story ran from the pull to an open pull request, then ghp done after the merge, with every GitHub write previewed, approved at a gate and then applied. On Spec Kit 1.2.1 it ran up to the push approval, with a reject at the first gate and a stale plan at the push gate (refused). The gate answers were typed by an AI agent that had read each preview; this is not a claim of independent human review.
  • Not verified: two-person approval, forks, organisation-owned Projects, rate limits, failed writes, the scheduled approval poller, Windows. The list is in the repository's docs/trust-and-limits.md.

Checklist

  • Valid workflow.yml (passes specify workflow info)
  • README.md with description, inputs, and step graph
  • LICENSE file included
  • GitHub release created with a tag-pinned raw URL
  • Added to workflows/catalog.community.json (alphabetical order), with sha256
  • Workflow tested end-to-end with specify workflow run (see Testing)

AI Disclosure

  • I did not use AI assistance for this contribution
  • I did use AI assistance (disclosure below)

AI disclosure: Tool: Claude Code (Anthropic's CLI/desktop app). Model: Claude Sonnet 5.5 for this pull request, the catalog entry and this text. Settings/mode: default settings, human-supervised (not autonomous): the submitter authorised filing it. Extent: the entry and this description were drafted by the AI and checked against the release artifacts (URL, sha256, file diff); the release code and tests were written with AI assistance under the submitter's direction. Replies to review comments may also be drafted by the AI and will be marked as such.

@praveenlavu
praveenlavu requested a review from mnriem as a code owner November 16, 2026 15:12
Copilot AI adaptive review requested due to automatic review settings November 16, 2026 15:12

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔵 Needs a closer look

The local diff cannot independently verify the externally hosted workflow’s pinned artifact, SHA-256, release contents, or GitHub write side effects, so human validation of the artifact and trust boundaries is required.

No open issues 🎉

What changed in this PR

Adds the ghp-lifecycle community workflow to Spec Kit’s discovery catalog and community documentation, with version-pinned release metadata and SHA-256 verification data.

Changes:

  • Adds the alphabetically ordered ghp-lifecycle version 0.1.2 catalog entry with its pinned URL, digest, requirements, integrations, license, and release metadata.
  • Updates the community catalog timestamp.
  • Documents the workflow in the community workflows listing.
File Description
workflows/​catalog.community.json Registers the pinned ghp-lifecycle workflow release and its metadata in the community catalog.
docs/​community/​workflows.md Adds the ghp-lifecycle workflow to the community workflow documentation listing.

Review effort: Lite (dynamic)

@mnriem mnriem added the triage-must-have Verdict: high-value, important work for Spec Kit — do first label Nov 16, 2026

This branch has not been deployed

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

Labels

triage-must-have Verdict: high-value, important work for Spec Kit — do first

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants