# Changelog
All notable changes to this project are documented here. The format is based on
[Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and this project adheres
to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
## [0.8.0] - 2026-07-11
### Added — C# / .NET ecosystem support
- New **language** ecosystem: C# / .NET (`*.csproj` detection via
`has_csproj` glob, SDK-style projects). `select_csproj` picks
deterministically: sort by filename, prefer `OutputType=Exe`, skip
`WinExe` (GUI, no stdout), lexicographic tiebreak. `csharp_cli_candidate`
emits `dotnet run --project <csproj> --` (trailing `--` separator so
appended `--help` reaches the app, not dotnet). Cursor globs:
`["*.cs", "*.csproj", "*.sln"]`. CI adds `setup-dotnet@v4` (net8.0).
Fixture `tests/fixtures/repos/csharp-cli/` with SDK-style csproj +
`Program.cs` `--help` handler. Integration test `#[ignore]`-gated
(self-skips without dotnet, pre-builds with `dotnet build -v q`).
## [0.7.0] - 2026-07-11
### Added — multi-ecosystem depth + language coverage
- Two new **language** ecosystems: PHP (`composer.json`) and JVM (Maven
`pom.xml` + Gradle `build.gradle`/`.kts`). Introspection detects manifests,
extracts name/version/authors, and resolves CLI candidates (`php_cli_candidate`
mirrors `node_cli_candidate` with `php` runtime + `bin` script resolution;
`jvm_cli_candidate` probes pre-built Gradle `installDist` scripts + Maven/
Gradle shaded jars — no build invocation, pure filesystem reads per design
§6.3). Cursor globs derive from language: PHP `["*.php", "composer.json"]`,
JVM `["*.java", "*.kt", "*.scala", "pom.xml", "build.gradle",
"build.gradle.kts"]`.
- **Cursor `globs` frontmatter** now derived from detected language for
auto-attach (was missing entirely — generated Cursor rules wouldn't
trigger on real work).
- **OpenCode `mode` frontmatter** now derived from project shape (`primary`
for CLI tools, `subagent` for libraries); previously hardcoded `subagent`.
- **Template refactor**: 4 near-identical ecosystem templates → shared
`skill_body.md.tera` partial + per-target frontmatter-only wrappers.
Adding a 6th `Target` is now ~10 lines instead of ~60.
- New insta snapshots for Cursor, OpenCode, Copilot, PHP-Cursor, JVM-Cursor
lock rendered output from regression.
- CI matrix adds `setup-php` and `setup-java` for cross-OS runtime coverage
on `--include-ignored` round-trip tests.
### Changed
- `Language::Php`, `Language::Jvm` variants extend the `Language` enum and
every match site (`category_hint`, `cursor_globs_hint`, introspect
`detect_language`, manifest name/version/authors, `primary_cli_candidate`).
- `cli.rs` `about` string updated to name all 5 agent ecosystems (was
leaking "Claude Code skill packs" into `--help`).
## [0.6.4] - 2026-07-11
### Fixed — Windows spawn + report normalization
- **`\\?\` UNC prefix from `std::fs::canonicalize` broke node module loading
on Windows**. `canonicalize` returns `\\?\C:\path\bin\cli.js` on Windows; the
kernel's `CreateProcess` accepts that for native exes, but Node's V8 module
loader rejects `\\?\` paths — `node \\?\C:\foo\cli.js --help` exits non-zero
→ `verify`'s `invocation.help_present` fired `RanNonZero` → init's critical
gate failed → init refused to write on Windows. New `canonicalize_for_argv`
helper strips the `\\?\` prefix post-canonicalize, applied at the rust,
node, and ruby CLI candidate sites. Unix is a no-op.
- **`HELP_TIMEOUT` raised 8s → 15s**. Windows CI's cold-cache `go run .
--help` first-compile cost (GOCACHE build + AV scan) exceeded 8s, false-
timing-out the go round-trip test. 15s covers CI cold-cache compile
while still bounding hung CLIs (a CLI that can't print `--help` in 15s is
not one an agent should invoke anyway, so the cap doubles as fail-safe).
- **`verify` report paths normalized to forward slashes**. `discovery.rs`
rendered relative paths via `path.strip_prefix(root).to_string_lossy()`,
which on Windows emits `skills\skillpack\SKILL.md` — but the marketplace
schema requires forward-slash-only paths, snapshot tests pin forward
slashes, and downstream tools grep the report on `/`. New `rel_unix`
helper (replace `\` with `/`) applied at the SKILL.md, .mdc, OpenCode
agent, and Copilot instructions check sites. Unix unchanged.
## [0.6.3] - 2026-07-11
### Fixed — Windows rust CLI detection
- **`rust_cli_candidate` missed built artifacts on Windows**. The fn joined
`target/{release,debug}/<name>` with the bare name, but `cargo build` on
Windows writes `<name>.exe`. `p.exists()` returned false → `has_cli=false`
on a real built CLI → `doctor` falsely reported no CLI and `verify`'s
invocation checks descended into the `not_runnable_here` warning path +
critical gate failure, refusing to write init output on Windows. Now
appends `.exe` on Windows (`cfg!`), leaves Unix untouched. The PATH
fallback already handles PATHEXT via `which_on_path`.
## [0.6.2] - 2026-07-11
### Fixed — Windows build correctness
- **Three lib tests failed on Windows** (introduced/exposed by the 0.6.1
matrix; the code was unix-only before). All three now cross-OS:
- `python_candidate_uses_m_module_when_importable` asserted
`argv[0].ends_with("python")`; the PATHEXT fix correctly resolves
`python.exe`, so the old assert rejected a valid Windows path. Replaced
with a `Path::file_stem().eq_ignore_ascii_case("python")` check that
accepts `python`, `python.exe`, `python3.exe`, etc.
- `node_cli_detected_via_bin_absolute_argv` had the same `ends_with("node")`
bug plus a string-suffix `script.ends_with("bin/cli.js")` that misses on
`\`-separated Windows paths. Now uses `Path::ends_with` (component-aware,
cross-OS) for the script tail + `file_stem` for the node binary stem.
- `skill_md_has_description_and_when_to_use_in_frontmatter` failed because
the repo had no `.gitattributes`: a Windows checkout with the default
`core.autocrlf=true` converted the `.tera` template sources to CRLF,
`include_str!` pulled CRLF bytes, Tera preserved them, and the generated
SKILL.md started with `---\r\n` instead of `---\n`. The real fix is not a
test-string patch — a generated SKILL.md shipping with CRLF on Windows
and LF on Unix violates byte-identical output. Added `.gitattributes`
pinning `*.tera` (and the rest of the source) to `eol=lf`, so templates
keep LF on every checkout regardless of the host's autocrlf setting.
## [0.6.1] - 2026-07-11
### Fixed — CI
- **Windows CI hard-failed on `unused_imports`**: `src/spawn.rs` test module
imported `use super::*` but every test fn inside is `#[cfg(unix)]`, so Windows
compiled the import with zero usages → `clippy -D warnings` turned the
`unused_imports` warning into a hard error. The new windows-latest matrix
entry surfaced this pre-existing bug (the 0.6.0 PATHEXT work was unrelated).
The import is now `#[cfg(unix)] use super::*` to match the tests it serves.
## [0.6.0] - 2026-07-11
### Added — Cross-platform CI matrix
- **CI now runs on ubuntu-latest, macos-latest, and windows-latest**, not
just ubuntu. The matrix uses the official `setup-node`, `setup-python`,
`setup-go`, and `ruby/setup-ruby` actions so every OS gets working runtimes
without hand-rolled apt/choco/brew logic. A previously-unchecked Windows
build regression would have shipped undetected.
### Fixed — Windows PATH resolution (PATHEXT)
- **`which_on_path` now enumerates `PATHEXT` on Windows**. `cmd.exe` appends
`PATHEXT` (`.EXE;.CMD;.BAT;…`) to a bare name; Rust's `Command::new` does
not, so probing `"node"` missed `node.exe` and `has_cli` silently reported
`false`. The probe now checks `name` plus `name{ext}` for each PATHEXT
entry on Windows; Unix path lookup is unchanged.
- **Three CLI candidates discarded the resolved binary path and re-spawned
the bare name**, which defeats PATHEXT resolution even when `which_on_path`
finds the binary. `rust_cli_candidate`, `python_cli_candidate`, and
`ruby_cli_candidate` now use the resolved `PathBuf` as `argv[0]` (the
`node_cli_candidate` pattern), so the spawn finds the real
`node.exe`/`python.exe`/`ruby.exe` on Windows instead of failing with
`NotFound`. The README "Platform" caveat is retired — Windows now works.
### Tests
- `which_on_path_returns_existing_file` sanity-checks that a PATH lookup
returns a real file on every CI OS. The PATHEXT-specific branch is
exercised end-to-end by the new windows-latest CI matrix entry against
real `cmd.exe` / `node.exe` lookups, not a racy synthetic env mutation.
## [0.5.1] - 2026-07-11
### Fixed — Template correctness (BLOCKER)
- **Double-escaped `one_line_description` in generated output**: the YAML-escaped
value was reused in markdown bodies and JSON templates, producing literal `\"`
in skill files and marketplace/plugin JSON. The render context now exposes two
keys: `one_line_description` (YAML-escaped, frontmatter only) and
`one_line_description_raw` (raw, used in markdown bodies + JSON). Both JSON
templates pipe through `json_encode | safe`; the markdown templates emit raw.
- **Dangling sentences from `{%-` trim markers**: all four markdown templates
(`SKILL.md`, `cursor-rule.mdc`, `opencode-agent.md`, `copilot-instructions.md`)
used Tera `{%-`/`-%}` whitespace-trim markers that over-trimmed and glued
headings to preceding content. Rewritten to bare `{% if %}` tags on own lines
(no trim markers); the tag emits nothing but its source-line `\n` survives as
exactly one blank line. Inline tags (`{% if cond %}content{% endif %}`) on the
same line as content emit no extra newlines.
- **Empty sections rendered when phrases/flags absent**: the "When to use"
section now wraps in `{% if when_to_use_phrases %}...{% endif %}` and the
flags intro+loop wraps in `{% if documented_flags %}...{% endif %}` across
all four markdown templates. A library with no `when_to_use_phrases` no longer
emits a "When to use" heading with an empty bullet list.
### Fixed — Introspection bugs
- **`HELP_TIMEOUT` divergence**: `introspect.rs` used 5s while
`verify::invocation` used 8s — a CLI that printed help in 6s passed verify but
had its flags dropped during `init` introspection (silent false-negative).
Unified to a single `pub const HELP_TIMEOUT: Duration = Duration::from_secs(8)`
in `spawn.rs`; both call sites import it.
- **Go module line trailing comment bleed**: `project_manifest_name` for Go
trimmed outer whitespace only, so `module github.com/foo/bar // bar tool`
produced a module name of "tool" (or worse) by taking the last `/`-segment
of the comment-bleeded path. Now takes the first whitespace-delimited token
before splitting, correctly yielding "bar". New test:
`go_module_name_strips_trailing_line_comment`.
- **Workspace walk early-return on nameless member**: `walk_cargo_workspace`
and `walk_npm_workspace` used `?` on the `member_name` resolution, so a
single member manifest with no resolvable name aborted the entire walk —
hiding CLI detection for every *other* member and silently reporting
`has_cli=false`. Replaced with `let ... else { diag.push(...); continue; }`
so the walk skips the pathological member and continues. New tests:
`walk_cargo_workspace_continues_past_no_artifact_member`,
`walk_npm_workspace_continues_past_no_cli_member`.
- **`detect_repo_url` git hang**: spawned `git remote get-url origin` with no
timeout — a credential-prompt stall (`git@github.com` with no SSH agent on a
fresh host) blocked introspection indefinitely. Routed through
`spawn_with_timeout(&mut cmd, Duration::from_secs(3))`; `RanClean` returns
the trimmed URL, all other `SpawnOutcome` variants return `None`.
### Fixed — Verify discovery sentinels
- **Empty ecosystem directories passed silently**: a `.codex/skills/` directory
that existed but contained no `SKILL.md` (e.g. files removed after init)
passed verify with no check emitted — a silent false-negative. Added
`.missing` fail sentinels for empty `.codex/skills/`, `.cursor/rules/`, and
`.opencode/agents/` directories. New check ids:
`discovery.codex.skill.missing`, `discovery.cursor.mdc.missing`,
`discovery.opencode.agent.missing`. New test:
`codex_empty_skills_dir_fails_verify`.
- **Copilot frontmatter passed verify**: a `.github/copilot-instructions.md`
starting with a `---` frontmatter block passed verify (the existing heading
check fired on the YAML content). The Copilot spec says "plain markdown, no
frontmatter" — now a `---` prefix triggers
`discovery.copilot.instructions` at fail severity before the heading check.
New test: `copilot_frontmatter_fails_verify`.
### Added — Test coverage
- **All-5-targets round trip**: `all_five_targets_init_then_verify_round_trip`
asserts `init --target claude --target cursor --target codex --target opencode --target copilot`
emits all 5 files and `verify` passes with all 5 `discovery.*` check ids at
`pass` severity.
- **Discovery.empty on bare repo**: `verify_on_empty_repo_fails_with_discovery_empty`
asserts a repo with no ecosystem files emits `discovery.empty` at fail severity.
- **Self-dogfood all ecosystems**: `self_dogfood_verify_asserts_all_ecosystems`
runs `verify` against the skillpack repo itself and asserts all 6 check ids
(marketplace, skill, cursor.mdc, codex.skill, opencode.agent, copilot.instructions) pass.
- **Doctor on plain Rust CLI**: `doctor_on_plain_rust_cli_reports_has_cli_true`
builds the `rust-cli` fixture, runs `doctor`, and asserts `has_cli: true`.
## [0.5.0] - 2026-07-10
### Added — `doctor` subcommand
- **`skillpack doctor`** — diagnose why introspection chose `has_cli` / language
as it did. Prints the detected profile + a chronological decision trace
(every falsy branch in `detect_cli` / `detect_language` pushes a `DiagNote`
explaining why a candidate was rejected). Read-only, exits 0. Answers the
user's "what happens with monorepos / workspaces / uv / poetry?" question
directly: the trace explains the workspace walk and the uv/poetry gap.
### Added — Workspace member walking
- **Cargo workspace support**: a workspace-only `Cargo.toml` (no `[package]`)
no longer silently reports `has_cli=false`. Introspection now walks
`[workspace].members`, probes each member crate's built/installed binary,
and derives the profile name from the member that ships the CLI.
- **npm workspace support**: a root `package.json` with `workspaces` but no
`bin` walks member packages, probing each for a `bin` entry.
- **uv / poetry**: explicitly diagnosed as "member walking not yet
implemented — run `skillpack init` in the member dir" (honest gap, no
false promise).
### Added — OpenCode + GitHub Copilot targets
- **`--target opencode`**: emits `.opencode/agents/<name>.md` with
`description` (required) + `mode` frontmatter per opencode.ai/docs/agents.
`verify` validates the frontmatter (`discovery.opencode.agent.*` check ids).
- **`--target copilot`**: emits `.github/copilot-instructions.md` (plain
markdown, no frontmatter) per docs.github.com/copilot. `verify` checks
the file is non-empty and starts with a `#` heading
(`discovery.copilot.instructions` check id).
- The repo's own committed distribution now dogfoods all 5 ecosystems.
## [0.4.0] - 2026-07-10
### Added — Multi-ecosystem verify (design §3 Phase 4)
- **`verify` now checks the Cursor and Codex distribution files**, not just
Claude's. Previously `init --target cursor --target codex` emitted those
files but `verify` silently ignored them — a broken `.mdc` or Codex
`SKILL.md` would pass `verify` and ship undetected. The discovery suite
now runs per-ecosystem:
- **Cursor** (`.cursor/rules/<name>.mdc`): new `check_one_mdc` parses the
YAML frontmatter and fails on a missing/empty `description` or a
description over the 1,536-char listing cap, warns on a missing or
non-boolean `alwaysApply`. Schema sourced from cursor.com/docs/rules
(verified July 2026).
- **Codex** (`.codex/skills/<name>/SKILL.md`): reuses the existing
`check_one_skill_md` validator with a distinct `discovery.codex.skill`
check_id prefix — same `SKILL.md` frontmatter shape as Claude, different
output path.
- Check ids are namespaced per ecosystem (`discovery.skill.*`,
`discovery.codex.skill.*`, `discovery.cursor.mdc.*`) so a CI report
names *which* ecosystem file drifted.
### Fixed
- **`verify` no longer hard-fails on a missing `.claude-plugin/`** — the
`marketplace.json` / `plugin.json` checks now run only when the Claude
distribution directory is present. A `--target cursor`-only pack
(legitimately without `.claude-plugin/`) was previously blocked by a
false positive `discovery.marketplace.missing` failure; `verify` now
skips the Claude checks entirely. An empty repo (no ecosystem files at
all) still emits a single `discovery.empty` failure so a typo'd `verify`
doesn't silently pass.
### Notes
- The human `verify` report now prints the per-file message for passing
checks (previously suppressed), so multi-ecosystem passes are visually
distinguishable (e.g. `skills/skillpack/SKILL.md validates` vs
`.codex/skills/skillpack/SKILL.md validates`). JSON output was already
per-file.
- Schema constants live in `src/verify/schema.rs` with cited sources:
`CLAUDE_PLUGIN_DIR`, `CODEX_SKILLS_DIR`, `CURSOR_RULES_DIR` join the
existing `PLUGIN_JSON_PATH` / `MARKETPLACE_JSON_PATH`.
- Invocation drift still runs against the first documented CLI's
SKILL.md only (design §5.2 step 3, unchanged from 0.2.1). Cursor/Codex
bodies are identical to the Claude SKILL.md body (same template), so a
Claude invocation-drift pass transitively validates the parallel
ecosystem files — per-ecosystem invocation drift is deferred to when a
pack legitimately ships divergent CLI surfaces per ecosystem.
## [0.3.0] - 2026-07-10
### Added — Multi-ecosystem emitter (design §3 Phase 4)
- **`--target` flag on `init`** — generate distribution files for multiple
agent ecosystems in a single run. Repeatable: `--target claude --target
cursor --target codex`. Defaults to `claude` only (backward compatible).
New `Target` enum (`Claude`, `Cursor`, `Codex`) drives `render_targets`,
which dispatches per ecosystem:
- **Claude** (unchanged): `.claude-plugin/marketplace.json` +
`plugin.json` + `skills/<name>/SKILL.md`.
- **Cursor**: `.cursor/rules/<name>.mdc` — YAML frontmatter
(`description`, `alwaysApply: false`) + rule body. Matches the Cursor
`.mdc` format documented at cursor.com/docs/rules.
- **Codex**: `.codex/skills/<name>/SKILL.md` — same `SKILL.md` frontmatter
as Claude (cross-agent-compatible), different output path per Codex's
`.codex/skills/` convention.
- **Self-dogfood** now generates all three: the repo is installable as a
Cursor rule (`@skillpack`) and a Codex skill (`.codex/skills/skillpack/`)
in addition to `claude plugin marketplace add nordicnode/skillpack`.
### Notes
- `verify` remains Claude-only for V1; cursor/codex files are emitted but
not yet checked by the discovery/invocation suite. Multi-ecosystem verify
is a follow-up.
- `--target` is CLI-only (not persisted in `skillpack.toml`); targets are a
per-run choice, not project metadata.
## [0.2.5] - 2026-07-10
### Fixed
- **`plugin.json` author defaulted to `Unspecified`** — same drift class as
the version fix in 0.2.4: `generate` fell back to the template's
`"Unspecified"` sentinel whenever the interview / `skillpack.toml` didn't
supply an author, ignoring the manifest entirely. `introspect` now reads
the first author from `Cargo.toml [package].authors`, `package.json
"author"` (string or `{ name }` object), `pyproject.toml [project].authors`,
and `*.gemspec spec.authors`. `generate` resolves `intent.author` with
`profile.authors` as fallback, so a non-interactive `init` (the CI path,
where no interview happens) still emits a real author. The Cargo
`"Name <email>"` format is stripped to the display name only — `author.name`
in the plugin schema is a display name, not a contact record.
### Added
- **`discovery.plugin.author` verify check** — warns when `plugin.json` has
no author or defaults to `"Unspecified"`, with a suggestion pointing at
the manifest key to set. Parallel to `discovery.plugin.version` (0.2.4).
## [0.2.4] - 2026-07-10
### Fixed
- **`plugin.json` version hardcoded `0.1.0`** — `generate::build_context`
emitted a literal `"0.1.0"` regardless of the project's real version. An
agent installing via a marketplace would see the wrong version signal for
every skill pack `skillpack` produced — the exact class of distribution-
layer drift `verify` exists to catch, yet `verify` itself never checked the
field. `introspect` now reads the version from the language manifest
(`Cargo.toml [package].version`, `package.json "version"`,
`pyproject.toml [project].version`, `*.gemspec spec.version`), stores it
on `ProjectProfile`, and `generate` passes it through to the template. Go
(`go.mod` has no version field) and manifests lacking a version key yield
an empty `version` rather than a fake sentinel — the honest signal.
### Added
- **`discovery.plugin.version` verify check** — warns on a missing or empty
`version` field in `plugin.json`, with a suggestion pointing at the
manifest key to set. Surfaced by the self-dogfood below: the old code
shipped `0.1.0` for a `0.2.3` crate and `verify` never flagged it.
- **Self-dogfood** — `skillpack` now generates and verifies its own skill
pack (`skills/skillpack/SKILL.md`, `.claude-plugin/marketplace.json`,
`.claude-plugin/plugin.json`) via a committed `skillpack.toml`. Closes the
Phase-1 §10 "use it on yourself" gap; the repo is now installable as
`claude plugin marketplace add nordicnode/skillpack`.
## [0.2.3] - 2026-07-10
### Fixed
- **Pipe-deadlock on >64KB `--help`** — subprocess spawns in `introspect`
(`spawn_with_timeout`), `verify::invocation` (`run_help` + `spawn_capture`)
piped stdout/stderr but only drained pipes *after* the child exited. A CLI
whose help output exceeded the ~64KB pipe buffer would block on the write,
`try_wait` would keep returning `Ok(None)`, and the deadline fired → false
`TimedOut`. Extracted a shared `spawn::run` helper that drains pipes on
reader threads while polling, killing + reaping on timeout. The new boundary
replaces the hand-rolled poll loops in all three call sites.
- **Byte-slice panic on multibyte README hints** — `print_profile` (`--verbose`)
truncated the description hint with `&hint[..120]`, slicing by byte index.
A multibyte UTF-8 char across byte 120 (emoji, CJK, accented — common in
real OSS) panicked with "byte index 120 is not a char boundary" →
`catch_unwind` → false `INIT_FATAL` exit for a display-only path. Fixed to
truncate by chars: `hint.chars().take(120).collect::<String>()`.
- **`coerce_kebab` leading-digit names** — names starting with digits (e.g.
`"123foo"`) passed through unchanged, but the schema regex
`^[a-z][a-z0-9-]*[a-z0-9]$` requires a letter first. The generated
`marketplace.json` / `plugin.json` name would then fail `verify`'s own
`is_valid_kebab` check. Now strips leading digits + re-trims hyphens,
falling back to `"tool"` if the result is empty.
### Added
- **Subcommand-drift e2e coverage** — the `capture_subcommand_help` (introspect)
and `check_subcommand_drift` (verify) code paths — real spawn reassembly of
`<base> <sub> --help` — were reasoned about but never exercised against a
compiled CLI (every fixture set `cli_subcommand_help: Vec::new()`). Added a
zero-dep `subcommand-cli` fixture with a hand-rolled clap-shaped `Commands:`
section + per-subcommand `--help`, and an integration test asserting the
generated `SKILL.md` contains `### Subcommands` with real sub names/flags and
`verify --format json` emits `invocation.subcommand_drift` pass results.
## [0.2.2] - 2026-07-09
### Fixed
- Generated `SKILL.md` "When NOT to use" prose no longer reads as broken
grammar ("outside the systems programming it was built for") — `category_hint`
now yields a noun per language ("the Rust tooling", "the JavaScript/Node
tooling", etc.).
- `verify --format json` now reports per-check `severity: "pass"` for passes,
matching the `counts.pass` key. Previously it emitted `"ok"` for a passed
check while the aggregate `counts` object used `pass` — two words for one
concept in the same payload.
- Removed the dead `has_cli` field from `VerifyInput` / `InvocationInput`.
CLI *presence* is derived from the SKILL.md itself, not the introspected
binary, so the field was threaded in but never read.
## [0.2.1] - 2026-07-09
### Fixed
- `init` now distinguishes its exit codes per design §8.1: a fixable
verify critical that the user declines to keep exits `INIT_FIXABLE` (2),
not the clean-abort `INIT_ABORTED` (1); fatal errors (introspect / render /
I/O) still exit `INIT_FATAL` (3). Previously the interactive decline path
returned 1, collapsing the fixable/fatal contract.
- Removed a redundant second `wait` in both spawn helpers
(`introspect::spawn_with_timeout`, `verify::invocation::run_help`): the
piped stdout/stderr are drained by a single `wait_with_output`, whose exit
status is used rather than re-reading the one `try_wait` already probed.
### Changed
- The invocation check is documented (README + design §5.2) as running
against the first documented CLI; discovery checks still cover every
`SKILL.md` in a multi-skill plugin. `init` only ever emits one skill, so
per-skill spawn plumbing is deferred until a CLI-backed multi-skill plugin
is a real case.
## [0.2.0] — 2026-07-09
### Fixed
- `init` no longer emits a `when_to_use: "(unspecified)"` placeholder when no
trigger phrases are given — it emits an empty `when_to_use`, so `verify`'s own
emptiness warning now fires honestly. Previously a generated skill with no
triggers would pass `verify` silently (the "looks fine until an agent tries
it" failure mode).
- `verify`'s invocation/flag-drift check now derives CLI presence from the
`SKILL.md` itself (a `## Invocation` section, or a fenced block with
`--flags`), not from whether introspect found a built binary on the local
machine. Hand-written packs that document a CLI but ship no source tree now
get a visible warning instead of a silent "pure-library" skip.
- `--debug` now prints every subprocess spawn in `verify` (it was previously a
no-op for the `verify` subcommand).
- `--accept-warnings` now matches its docs: in interactive mode, `verify`
warnings prompt before writing; `--accept-warnings` skips the prompt.
`--non-interactive` warnings never block (CI gates on criticals only).
- The `property_proptest.rs` placeholder is now a real property test exercising
`extract_flags` and `parse_skill_frontmatter` directly (the lib re-exports it
already exposed).
### Added
- `verify --format json`: machine-readable report with per-check ids, counts,
and an `ok` flag, for CI gating / scripting.
- Reverse flag-drift warning: `--help` flags the skill doesn't document are
reported as a warning (discoverability gap for an agent).
- Multi-skill verification: `verify` checks every SKILL.md under `skills/`
(sorted, deterministic) instead of an arbitrary first one.
- `--format`, scoped flag-drift extraction (the documented invocation area,
not the whole body), and a testable confirmation path for the pre-commit gate.
### Changed
- `tempfile` is now a runtime dependency; the hand-rolled `mod tempfile` in
`main.rs` is removed.
## [0.1.0] — 2026-07-09
### Added
- `skillpack init` — introspect a repo (Rust, npm, Python, Go, Ruby), interview
the maintainer (or run non-interactive from `skillpack.toml`), and generate
the three Claude Code distribution files (`marketplace.json`, `plugin.json`,
`SKILL.md`). Pure-library path when no CLI is detected (documents the install
+ import pattern instead of an invocation).
- `skillpack verify` — discovery checks (kebab-case + reserved-name validation,
1,536-char listing cap, `when_to_use` trigger phrases, `./`-prefixed paths)
and invocation checks (`--help` runs under timeout; every documented flag
exists in real `--help` output). Exits non-zero on critical failure for use
as a CI PR gate.
- Pre-commit verification: `init` runs the full `verify` suite against its own
output before writing files.
- `--non-interactive`, `--accept-warnings`, `--license <SPDX>`, `--verbose`,
`--debug` flags.
- GitHub Actions CI: `cargo fmt --check`, `cargo clippy --all-targets -D
warnings`, and `cargo test -- --include-ignored` (runs the Go + Ruby
`#[ignore]`-gated round trips where those runtimes are present).
- Insta snapshot tests pinning byte-identical output of all three generated
files for CLI and pure-library profiles.
- Test fixtures for rust, node, python, go, ruby CLIs and a node library;
a `broken-cli` fixture for drift detection.
### Toolchain
- Pin Rust 1.95.0 via `rust-toolchain.toml` so local and CI fmt/clippy agree.