[Extension]: Add Verify Review Ship

[cadugevaerd]

Extension ID

verify-review-ship

Extension Name

Verify Review Ship

Version

0.1.0

Description

Adds post-implementation verify, review, and ship readiness gates to Spec Kit workflows.

Author

Carlos Eduardo Gevaerd Araujo

Repository URL

https://github.com/cadugevaerd/spec-kit-verify-review-ship

Download URL

https://github.com/cadugevaerd/spec-kit-verify-review-ship/archive/refs/tags/v0.1.0.zip

License

MIT

Homepage (optional)

https://github.com/cadugevaerd/spec-kit-verify-review-ship

Documentation URL (optional)

https://github.com/cadugevaerd/spec-kit-verify-review-ship/blob/main/README.md

Changelog URL (optional)

https://github.com/cadugevaerd/spec-kit-verify-review-ship/blob/main/CHANGELOG.md

Required Spec Kit Version

=0.1.0

Required Tools (optional)

None. The extension contains Markdown command prompts, one optional lifecycle hook, and a configuration template.

Number of Commands

3

Number of Hooks (optional)

1

Tags

quality, review, shipping, workflow, testing

Key Features

• /speckit.verify-review-ship.verify: verifies implementation completeness against Spec Kit artifacts and project gates after /speckit.implement.
• /speckit.verify-review-ship.review: runs a structured five-axis review covering correctness, readability, architecture, security, and performance.
• /speckit.verify-review-ship.ship: synthesizes verification and review evidence into a GO/NO-GO readiness decision with rollback planning.
• Optional after_implement hook prompts users to run the verify gate after implementation.
• Config template supports project-specific gate commands and policy defaults.

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:

• Linux container with Spec Kit installed via uvx --from git+https://github.com/github/spec-kit.git
• Spec Kit initialized with Hermes integration
• Release archive URL: https://github.com/cadugevaerd/spec-kit-verify-review-ship/archive/refs/tags/v0.1.0.zip

Test project:

• Temporary throwaway Spec Kit project under /tmp/spec-kit-vrs-remote-test

Test scenarios:

1. Initialized a fresh Spec Kit project with:

   uvx --from git+https://github.com/github/spec-kit.git specify init . --integration hermes --ignore-agent-tools --script sh

2. Installed the extension from the release archive with:

   specify extension add verify-review-ship --from https://github.com/cadugevaerd/spec-kit-verify-review-ship/archive/refs/tags/v0.1.0.zip

3. Confirmed .specify/extensions/.registry registered version 0.1.0.
4. Confirmed all commands and aliases were registered for the Hermes integration:
   • speckit.verify-review-ship.verify
   • speckit.verify-review-ship.v
   • speckit.verify-review-ship.review
   • speckit.verify-review-ship.r
   • speckit.verify-review-ship.ship
   • speckit.verify-review-ship.s
5. Verified the remote raw extension.yml is accessible.
6. Downloaded the GitHub release archive and computed SHA-256:
   08af97697c6d73b1c1b927ded8cd77869e40a7379a50a5e1ea8e253e9da57bb4
7. Ran a local secret-pattern scan over extension source files. Hits were only documentation/prompt text references to secrets; no credentials or hardcoded tokens were found.

Example Usage

# Install extension from release archive
specify extension add verify-review-ship \
  --from https://github.com/cadugevaerd/spec-kit-verify-review-ship/archive/refs/tags/v0.1.0.zip

# Typical Spec Kit flow
/speckit.implement
/speckit.verify-review-ship.verify
/speckit.verify-review-ship.review
/speckit.verify-review-ship.ship

Proposed Catalog Entry

{
  "verify-review-ship": {
    "name": "Verify Review Ship",
    "id": "verify-review-ship",
    "description": "Adds post-implementation verify, review, and ship readiness gates to Spec Kit workflows.",
    "author": "Carlos Eduardo Gevaerd Araujo",
    "version": "0.1.0",
    "download_url": "https://github.com/cadugevaerd/spec-kit-verify-review-ship/archive/refs/tags/v0.1.0.zip",
    "sha256": "08af97697c6d73b1c1b927ded8cd77869e40a7379a50a5e1ea8e253e9da57bb4",
    "repository": "https://github.com/cadugevaerd/spec-kit-verify-review-ship",
    "homepage": "https://github.com/cadugevaerd/spec-kit-verify-review-ship",
    "documentation": "https://github.com/cadugevaerd/spec-kit-verify-review-ship/blob/main/README.md",
    "changelog": "https://github.com/cadugevaerd/spec-kit-verify-review-ship/blob/main/CHANGELOG.md",
    "license": "MIT",
    "requires": {
      "speckit_version": ">=0.1.0"
    },
    "provides": {
      "commands": 3,
      "hooks": 1
    },
    "tags": [
      "quality",
      "review",
      "shipping",
      "workflow",
      "testing"
    ],
    "verified": false,
    "downloads": 0,
    "stars": 0,
    "created_at": "2026-07-09T00:00:00Z",
    "updated_at": "2026-07-09T00:00:00Z"
  }
}

Additional Context

This extension is inspired by Addy Osmani's agent-skills Verify/Review/Ship workflow concepts and adapts them to the Spec Kit extension system using only broadly supported primitives: Markdown command files, extension.yml, an optional after_implement hook, and a config template.

It does not depend on any external subagent registry. If an agent supports subagents/tools, the ship command can ask it to run review/security/test passes in parallel; otherwise the command instructs the agent to perform those passes sequentially and label each report.

[cadugevaerd]

Note for maintainers: this was submitted using the Extension Submission template via the GitHub REST API. The account does not have permission to apply repository labels, so please apply extension-submission / needs-triage if required for automation.

[github-actions]

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

[github-actions]

Pull request created: #3450

Generated by Add Community Extension from Issue Submission · 307.2 AIC · ⌖ 15.1 AIC · ⊞ 32.9K

[github-actions]

All validation checks passed ✅ — a pull request has been created to add Verify Review Ship to the community catalog.

Validation summary:

• Extension ID verify-review-ship — valid format
• Version 0.1.0 — valid semver
• Repository public with extension.yml, README.md, and LICENSE present
• GitHub release v0.1.0 confirmed
• Download URL follows the archive pattern
• All testing and submission checklists checked

The extension was inserted alphabetically in extensions/catalog.community.json and docs/community/extensions.md.

Posted on behalf of @mnriem by GitHub Copilot (model: claude-sonnet-4.6, autonomous)

Generated by 🧩 Add Community Extension from Issue Submission for issue #3429 · 307.2 AIC · ⌖ 15.1 AIC · ⊞ 32.9K · ◷

[mnriem]

Thank you!