Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

[Extension]: Add SpecAssay Check (update to 0.5.1)

Aperta Adatta ai principianti
#4,690 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
2/5
Tempo stimato
1-3 ore
Idoneità per principianti
68/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
bash, python
Ambito
tooling

Direzione di ricerca

Individuare la voce di catalogo esistente di specassay-check e confrontarla con la Proposed Catalog Entry in questa issue. Aggiornare la voce esistente alla versione 0.5.1 con gli URL, i requisiti, i cinque comandi, i tag e i metadati forniti, quindi verificare che rimanga coerente con gli aggiornamenti del preset e del bundle associati.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

enhancement needs-triage
Extension ID

specassay-check

Extension Name

SpecAssay Check

Version

0.5.1

Description

Gate 2 refuses silent gaps and emits a trace-manifest (trace-manifest.json).

Author

Rik Dryfoos

Repository URL

https://github.com/rdryfoos/specassay

Download URL

https://github.com/rdryfoos/specassay/releases/download/v0.5.1/specassay-check-0.5.1.zip

License

MIT

Homepage (optional)

https://www.specassay.com

Documentation URL (optional)

https://github.com/rdryfoos/specassay/blob/main/extensions/specassay-check/README.md

Changelog URL (optional)

https://github.com/rdryfoos/specassay/blob/main/CHANGELOG.md

Required Spec Kit Version

=0.14.0,<2.0.0

Required Tools (optional)
- bash - required
- python3 (>=3.8) - required
Number of Commands

5

Number of Hooks (optional)

1

Tags

traceability, gate, ci, governance, sdd

Key Features
  • Gate 2 refuses a silent gap: an acceptance criterion with no test and no open tracked-debt task fails the build rather than passing quietly
  • Emits trace-manifest.json (v4) and trace-manifest.v5beta.json, one row per registry ID with its status and the evidence behind it
  • Five statuses, including retired for an intent withdrawn on purpose, so a withdrawal is never mistaken for a gap
  • Mints durable IDs at intent and refuses an ID the project's own configured grammar would reject
  • Coverage matrix and portfolio snapshot for CI and for cold readers
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

This updates the existing catalog entry from 0.4.12 to 0.5.1. It supersedes
issue #4252, filed at 0.4.12 and merged as catalog PR #4254, and replaces
#4649. Neither v0.4.13 nor v0.5.0 was ever filed, so this one carries three
releases of change.

Tested on: Linux, Spec Kit 1.0.5, Python 3.11.15, on 2026-09-20.
Previously captured on Spec Kit 1.0.4 at release time, 2026-09-17.
The >=0.14.0 floor was exercised at v0.5.1 on 2026-09-17: the bundle installs
and the Gate runs on 0.14.0, though that version does not scaffold the settings
file, so the Gate reports config: MISSING and continues on defaults.

sha256 of the submitted archive, re-confirmed against the published asset
2026-09-22:

$ curl -fsSL -O https://github.com/rdryfoos/specassay/releases/download/v0.5.1/specassay-check-0.5.1.zip
$ sha256sum specassay-check-0.5.1.zip
874728251c850e84d71f7a94dbdc326073703a8b408690d87a62b68d43dc6eff specassay-check-0.5.1.zip

Test scenarios, in a clean project (specify init . --here --force --non-interactive --integration claude):

  1. Installed direct from the download URL:
    $ specify extension add specassay-check --from
    installed; specify extension list reports SpecAssay Check (v0.5.1)
  2. Ran the Gate on an empty project. It refuses and names the fix:
    FAIL: registry not found: PRD.md
  3. Ran the Gate on an empty-but-present registry. Exit 0, and it prints the
    on-ramp naming both mint routes.
  4. Minted a first ID:
    $ bash .../mint-id.sh AC LOGIN --append "Given a wrong password, ..."
    AC-LOGIN-10
  5. Ran the Gate again. It refuses honestly, which is the intended first red:
    FAIL: registry ID missing from specs: AC-LOGIN-10
    FAIL: registry ID missing from tasks: AC-LOGIN-10
    FAIL: silent gap: AC-LOGIN-10 has no test and no open tracked-debt task
    exit 1
  6. Added a spec line and one open task carrying the ID, the documented way to
    clear it:
    SpecAssay Check (Gate 2): OK (1 registry IDs)
    exit 0, and trace-manifest.json reports AC-LOGIN-10 as tracked-debt.

The extension is also run against its own repository on every pull request,
where it currently reports OK on 71 registry IDs.

Example Usage
# Install from the release archive
specify extension add specassay-check --from https://github.com/rdryfoos/specassay/releases/download/v0.5.1/specassay-check-0.5.1.zip

# Mint a durable ID at intent
/speckit.specassay-check.mint AC LOGIN "Given a wrong password, when the user signs in, then the form shows an error and no session starts."

# Run Gate 2; a silent gap fails the build
/speckit.specassay-check.gate
Proposed Catalog Entry
{
  "specassay-check": {
    "name": "SpecAssay Check",
    "id": "specassay-check",
    "description": "Gate 2 refuses silent gaps and emits a trace-manifest (`trace-manifest.json`).",
    "author": "Rik Dryfoos",
    "version": "0.5.1",
    "download_url": "https://github.com/rdryfoos/specassay/releases/download/v0.5.1/specassay-check-0.5.1.zip",
    "repository": "https://github.com/rdryfoos/specassay",
    "homepage": "https://www.specassay.com",
    "documentation": "https://github.com/rdryfoos/specassay/blob/main/extensions/specassay-check/README.md",
    "changelog": "https://github.com/rdryfoos/specassay/blob/main/CHANGELOG.md",
    "license": "MIT",
    "category": "visibility",
    "effect": "read-write",
    "requires": {
      "speckit_version": ">=0.14.0,<2.0.0",
      "tools": [
        { "name": "bash", "required": true },
        { "name": "python3", "version": ">=3.8", "required": true }
      ]
    },
    "provides": {
      "commands": 5,
      "hooks": 1
    },
    "tags": ["traceability", "gate", "ci", "governance", "sdd"],
    "verified": false,
    "downloads": 0,
    "stars": 0,
    "created_at": "2026-08-13T00:00:00Z",
    "updated_at": "2026-09-20T00:00:00Z"
  }
}
Additional Context

Update to an existing entry, not a new extension. Replaces #4649.

provides.commands moves from 2 to 5. It has been stale since v0.4.13: dig,
matrix and portfolio shipped after the 0.4.12 entry was written. The five
are speckit.specassay-check.gate, .mint, .dig, .matrix and .portfolio.

Companion issues in this submission: the preset (updates #4253) and the bundle
(updates #4255). The bundle pins both component versions, so all three need to
land together or specify bundle install cannot resolve.

Lingua principale
Python
Stelle
138k
Fork
12.4k
Merge medio
3g 6h
PR unite (30g)
145

Guida per i contributori

Apri la guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di github/spec-kit

Tutte le issue di github/spec-kit

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.