jbaruch / jbaruch/coding-policy
docs(release): SKILL.md Step 7 restates two helpers' decision predicates
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1
- Forks
- 2
- Avg merge
- 9h 22m
- Merged PRs (30d)
- 81
Description
Summary
Advisory findings from #455's review round, deferred rather than folded (no blocking round was open; rules/review-severity.md Split Reading From Acting).
Two Step 7 bullets in skills/release/SKILL.md restate a helper's Boolean predicate, which rules/script-as-black-box.md "What Skills Do Not Restate" reserves for the script:
SKILL.md:194— restatesverify-publish-landed.sh's conjunction (conclusion == successANDLatest Version > PRE). Keep the invocation and the exit/output contract; point throughPUBLICATION.mdto the script header for the predicate.SKILL.md:200— restatesverify-github-release.sh's conjunction of run success, release existence, publication status and retrievable assets. Same treatment.
Presentation-only: no agent behavior changes either way, which is why neither gated.
Test plan
- Neither bullet names a predicate; both name the command and where its contract lives
-
PUBLICATION.mdstill carries each helper's exit-code contract, so nothing is lost by the cut
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with rules/script-as-black-box.md and inspect Step 7 in skills/release/SKILL.md around lines 194 and 200. Check the headers of verify-publish-landed.sh and verify-github-release.sh, then review PUBLICATION.md for their exit-code contracts. Done means both bullets invoke the commands without restating predicates and still point to the documented contracts.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 88/100