General-purpose coding policy for Baruch's AI agents
74
93%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
Nothing below runs until this exits 0:
KS=.tessl/plugins/jbaruch/coding-policy/skills/release/; [ -d "$KS" ] || KS="$HOME/$KS"; [ -d "$KS" ] || case "$(git config --get remote.origin.url)" in git@github.com:jbaruch/coding-policy|git@github.com:jbaruch/coding-policy.git|https://github.com/jbaruch/coding-policy|https://github.com/jbaruch/coding-policy.git|ssh://git@github.com/jbaruch/coding-policy|ssh://git@github.com/jbaruch/coding-policy.git) KS=skills/release/ ;; *) echo "coding-policy skill not found: run tessl install jbaruch/coding-policy" >&2; exit 1 ;; esac
bash "$KS/check-leftovers.sh" --releaseExit 0 clears this readiness gate. Read others and attention even on exit 0.
Preserve unrelated work and record its path, evidence, consequence and required
owner decision in the existing task report or standalone conversation. Continue
this release without committing, stashing, ignoring or deleting that work.
Exit 1 blocks on blocking; resolve only the selected checkout's authorized work
and re-run. Exit 2 is a usage or tool-state error, never a verdict.
The scope and observation contract live in skills/release/check-leftovers.sh
(header). The repository-wide inspection mode is not a release prerequisite.
main/master)rules/ or skills/ → rules/context-writing-style.md; new scripts → rules/script-delegation.md and rules/testing-standards.md)because, therefore, since, etc. per rules/context-writing-style.mdouter-boundary-process-contract token per rules/error-handling.mdbash -n <script> must exit 0 on shell scripts.tessl-plugin
rules
skills
migrate-to-plugin
onboard-repo
release
hooks
references