CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

jbaruch/coding-policy

General-purpose coding policy for Baruch's AI agents

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Overview
Quality
Evals
Security
Files

ci-safety.mdrules/

alwaysApply:
Yes

CI Safety

Required Read

  • Before branch, commit or CI work, authoring commit messages, reading or handling PR reviews, merges, publication, release-helper lookup, or any CI exception, read skills/coding-contracts/references/ci-safety.md in full.
  • Its full text and named sections bind as rule content.
  • Resolve the reference within its owning installed plugin.
  • Missing or unreadable content stops the affected action until the plugin is repaired.
  • Read explicitly when triggered.
  • Never @-import the reference.

Boundary

  • Do not change CI outside the authorized scope.
  • Never skip failing tests or bypass review.
  • Never push directly to protected branches outside a binding carve-out.
  • Watch every push to its required terminal gates.
  • Helper lookup grants no merge, publication, installation or operator authority.

README.md

tile.json