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
Once Step 1's readiness checks pass, create the PR automatically — the green readiness checks are the gate. Do not pause to ask a human whether to open it.
Push the branch: git push -u origin <branch>
Resolve origin's repository, so the PR opens where the branch was pushed and never in gh's own default (gh repo set-default):
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
python3 "$KS/origin-repo.py" .Contract: see skills/release/origin-repo.py — top-of-file docstring. Emits { "repo", "owner", "name" }. A non-zero exit stops the release with its stderr diagnostic
Create the PR with gh pr create --repo <repo>, <repo> from that output:
<type>(<scope>): <imperative summary>## Summary
<what changed and why — 1-3 bullet points>
## Test plan
- [ ] <verification steps>
Closes #<n>Closes #<n>, one line per issue the PR fully resolvesPart of #<n> for an issue it only partly resolvesPart of https://github.com/<owner>/<repo>/issues/<n> for partial work tracked in another repositoryNo issue for work with no tracking issueRefs #<n>, Related #<n> and a bare #<n> close nothingCheck the link GitHub resolved from the body:
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
python3 "$KS/check-closing-issues.py" <owner> <repo> <pr-number>Exit 0 passes
Exit 1 (unlinked): the body names no issue GitHub will close and declares no alternative. Edit the body and re-run
Exit 2 is a usage, environment or gh error
Output fields and verdicts are the script's contract — see skills/release/check-closing-issues.py docstring
When this step is wrapped in a reusable script (e.g., release.sh that other devs run unattended), see the script-wrapping gates at:
skills/release/references/SCRIPTING.mdProceed immediately to Step 3.
.tessl-plugin
rules
skills
migrate-to-plugin
onboard-repo
release
hooks
references