[Extension]: Add SpecKit Companion v0.27.0 (catalog update)

Ouverte Adaptée aux débutants
  • Quelque chose ne va pas ?
#5,422 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
2/5
Temps estimé
1-3 heures
Accessibilité débutants
68/100
Type d'issue
Fonctionnalité
Clarté
Clairement spécifiée
Activité
Active
Stack technique
github, python
Domaine
release, tooling

Piste de recherche

Lis l'entrée de catalogue proposée et compare-la à l'entrée existante du catalogue Spec Kit pour SpecKit Companion, en particulier à l'entrée v0.26.0 mentionnée dans le ticket #5324. Mets à jour les métadonnées du catalogue vers v0.27.0 et supprime le tag living-specs retiré ; vérifie que l'entrée correspond au manifeste et aux détails de la version indiqués dans le ticket.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

Extension ID

companion

Extension Name

SpecKit Companion

Version

0.27.0

Description

Records your spec-kit runs live: status, resume, and a health check for what actually happened.

Author

alfredoperez

Repository URL

https://github.com/alfredoperez/speckit-companion

Download URL

https://github.com/alfredoperez/speckit-companion/releases/download/speckit-ext-v0.27.0/companion-0.27.0.zip

License

MIT

Homepage (optional)

https://github.com/alfredoperez/speckit-companion/tree/main/apps/speckit-extension

Documentation URL (optional)

https://github.com/alfredoperez/speckit-companion/blob/main/apps/speckit-extension/README.md

Changelog URL (optional)

https://github.com/alfredoperez/speckit-companion/blob/main/apps/speckit-extension/CHANGELOG.md

Required Spec Kit Version

=1.2.5.dev0

Required Tools (optional)
- `python3` (optional)
Number of Commands

19

Number of Hooks (optional)

10

Tags

vscode, progress, hooks

Key Features
  • Hands-off runs on Spec Kit's workflow engine — specify workflow run speckit-companion routes on the recorded size, and each review gate resumes headless
  • Hands-off runs cost less — fewer bookkeeping calls and fewer instructions, closing the gap to stock on harder work
  • Size is decided before the spec — a change you understand, with nothing risky in it, goes straight to implement
  • A test task for every requirement — each is checked through the screen or API in the condition it names
  • Corner cuts recorded as concerns — a skipped test, a suppression, an empty stub or a lower coverage bar is kept with its file and line, never blocking
  • Specs finish at Completed — a run no longer stops at Implemented when converge adds work
  • Living specs retired — each change keeps one folder, and doctor flags leftover living-spec settings
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 Darwin 27.0.0 with Spec Kit 1.4.1.dev0.

  • Upgraded a project to v0.27.0 from the published release zip; the retired living-spec skills were removed.
  • Ran a real feature hands-off with Claude Code in a terminal (auto on "starred todos"): it was sized simple and ended completed in one session, 25 turns, with a clean run record.
  • The extension's own suite passes (Python unit tests and shape parity).
Example Usage
# Install (Spec Kit 1.2.5 or newer)
specify extension add companion --from https://github.com/alfredoperez/speckit-companion/releases/download/companion-latest/companion.zip

# Run the whole pipeline hands-off on a new feature
/speckit.companion.auto Add a dark mode toggle to settings that survives a reload

# Or on Spec Kit's workflow engine, with review gates
specify workflow run speckit-companion --input spec="Add a dark mode toggle"

# Or step by step
/speckit.companion.specify Add a dark mode toggle to settings
/speckit.companion.plan
/speckit.companion.tasks
/speckit.companion.implement

# See where every spec stands, and check the install
/speckit.companion.status
/speckit.companion.doctor
Proposed Catalog Entry
{
  "companion": {
    "name": "SpecKit Companion",
    "id": "companion",
    "description": "Records your spec-kit runs live: status, resume, and a health check for what actually happened.",
    "author": "alfredoperez",
    "version": "0.27.0",
    "download_url": "https://github.com/alfredoperez/speckit-companion/releases/download/speckit-ext-v0.27.0/companion-0.27.0.zip",
    "sha256": "e8e2a62a55e030ec261ee5e3d475effb1b869a4f7abba5b4cd7e155f2133615b",
    "repository": "https://github.com/alfredoperez/speckit-companion",
    "homepage": "https://github.com/alfredoperez/speckit-companion/tree/main/apps/speckit-extension",
    "documentation": "https://github.com/alfredoperez/speckit-companion/blob/main/apps/speckit-extension/README.md",
    "changelog": "https://github.com/alfredoperez/speckit-companion/blob/main/apps/speckit-extension/CHANGELOG.md",
    "license": "MIT",
    "category": "process",
    "effect": "read-write",
    "requires": {
      "speckit_version": ">=1.2.5.dev0",
      "tools": [
        {
          "name": "python3",
          "required": false
        }
      ]
    },
    "provides": {
      "commands": 19,
      "hooks": 10
    },
    "tags": [
      "vscode",
      "progress",
      "hooks"
    ],
    "verified": false,
    "downloads": 0,
    "stars": 0,
    "created_at": "2026-06-11T00:00:00Z",
    "updated_at": "2026-11-13T00:00:00Z"
  }
}
Additional Context

Update from v0.26.0 (#5324) to v0.27.0. Living specs are retired in this release, so the tags follow the manifest and drop living-specs.

Langage dominant
Python
Étoiles
149k
Forks
13.4k
Merge moyen
1 j 5 h
PR mergées (30 j)
223

Préparer son environnement

Ouvrir dans Codespaces

Lance le conteneur de développement du projet dans votre navigateur, avec votre propre compte GitHub.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de github/spec-kit

Toutes les issues de github/spec-kit

Issues similaires

Plus d'issues Python

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.