fix(release-verify-rc): use placeholders in step-6 artefact example - #971
fix(release-verify-rc): use placeholders in step-6 artefact example#971Shaurya2k06 wants to merge 1 commit into
Conversation
Replace the concrete apache-airflow-2.11.0-source-release worked example with the skill's existing <artefact-source-release> token so the extension-stripping lesson stays project-agnostic. Signed-off-by: shaurya2k06 <shaurya2k06@gmail.com>
|
The placeholder swap is right in principle, but these lines are inside ## Step 6 — Binary exclusion check, and step-config.json extracts that step as the system prompt for step-6-binary-exclusion. Both of its cases expect paste_recipe to contain find apache-airflow-2.11.0-source-release …, and that field is judge-graded, so this is a prompt change with a fixture dependency. Could you run that suite before this merges? Note: I ran it and am seeing failures.
|
Summary
apache-airflow-2.11.0-source-releaseworked example inrelease-verify-rcstep 6 with the skill's existing<artefact-source-release>placeholder so the extension-stripping lesson stays project-agnostic.
.tar.gz/.zip),do not drop the
-source-releasesuffix.Type of change
.claude/skills/<name>/) — eval fixtures updated belowtools/<system>/*.md)tools/*/withpyproject.toml)docs/,README.md,CONTRIBUTING.md)projects/_template/)prek, workflows, validators)Test plan
uv run --project tools/skill-and-tool-validator skill-and-tool-validatepassestools/dev/check-placeholders.shpassesprek run --files skills/release-verify-rc/SKILL.mdpasses (includescheck-placeholders+skill-and-tool-validate)eval fixtures intentionally keep concrete names under the allowlisted
tools/skill-evals/evals/pathRFC-AI-0004 compliance
Linked issues
Closes #945