Openspec Apply Change

CLI-řízená smyčka OpenSpec apply: čtení kontextu změny, implementace úkolů, označení zaškrtávacích políček jako hotových

od VILA-Lab · VILA-Lab/FigMirror

Otestováno · Funguje ★ 7.6/10

Openspec Apply Change — CLI-řízená smyčka OpenSpec apply: čtení kontextu změny, implementace úkolů, označení zaškrtávacích políček jako hotových

Co umí

Orchestuje implementing tasks from an OpenSpec change by calling the openspec CLI (list/status/instructions apply --json) to detect the schema, enumerate context files, report progress, then working through pending tasks and flipping tasks.md checkboxes as it goes. Spouští se, když uživatel wants to start or continue implementing, or work through tasks in an OpenSpec change. Vyžaduje the @fission-ai/openspec CLI and an OpenSpec-initialized project.

Testovací report

Nainstalováno @fission-ai/openspec v1.7.0 (the bare `openspec` npm package is a dead 0.0.0 placeholder), cloned FigMirror, and ran every command the skill body specifies against the repo's own openspec/ project: `openspec list --json` (3 changes), `status --change` (schemaName spec-driven, artifactPaths), and `instructions apply --change --json` (returned contextFiles, progress {total:26,complete:14}, state:"ready", dynamic instruction, task list). Pro the output test I compared a baseline grep+edit against the skill flow: baseline counted 14/26 and flipped the first `- [ ]`; the skill produced the identical 14->15/26 result and next-task pick, but additionally surfaced schemaName, state, and the enumerated contextFiles (glob-resolved specs/**/*.md) that a grep does not. After flipping task 15's checkbox the CLI correctly re-derived progress to complete:15. Frontmatter se parsuje (name+description present), no security smells. Real friction: the frontmatter's "Requires openspec CLI" never names the @fission-ai/openspec package, and the skill points to a nonexistent openspec-continue-change sibling on blocked state.

Testováno: 2026-07-21 · Claude Code 2.x (agent harness)

Instalace

git clone --depth 1 https://github.com/VILA-Lab/FigMirror.git /tmp/openspec-apply-change-src
mkdir -p ~/.claude/skills
cp -R /tmp/openspec-apply-change-src/.claude/skills/openspec-apply-change ~/.claude/skills/openspec-apply-change
# Requires the OpenSpec CLI. The REAL package is @fission-ai/openspec — the bare `openspec` npm name is a dead 0.0.0 placeholder with no bin:
#   npm install -g @fission-ai/openspec   # provides the `openspec` command (tested v1.7.0)
# Needs an OpenSpec-initialized project: openspec/changes/<name>/ with tasks.md. Run `openspec init` in your repo if absent.
# The skill runs: openspec list/status/instructions apply --json, then edits tasks.md `- [ ]` -> `- [x]`.
# Sibling skill it suggests on blocked state (openspec-continue-change) is NOT present in this repo.

Příkazy a ukázkové prompty

  • /openspec-apply-changeCLI-řízená smyčka OpenSpec apply: čtení kontextu změny, implementace úkolů, označení zaškrtávacích políček jako hotových

Skilly se spouštějí běžnými požadavky — žádné příkazy k zapamatování. Po instalaci ho aktivují prompty jako tyto (anglicky):

  • Start implementing this OpenSpec change
  • Continue working through the OpenSpec tasks
  • Pick up where the last OpenSpec task left off