Coding policy tile for Baruch's AI agents. Language-agnostic code quality rules plus Tessl-specific plugin authoring standards — covering commits, testing, error handling, skill structure, script delegation, and eval quality.

What's New

12 always-on steering rules: 8 covering code quality, 4 covering plugin authoring
release skill — structured PR + merge workflow with Copilot review
eval-authoring skill — generate, review, and curate eval scenarios
Language-agnostic: works with any stack, no Python/JS assumptions

See CHANGELOG.md for full version history.

Installation

tessl install jbaruch/coding-policy

What's Included

Category	Rule	Summary
Git	commit-conventions	Imperative mood, one change per commit, PR hygiene
Testing	testing-standards	Outcome-based, deterministic, no binary fixtures
Errors	error-handling	Specific exceptions, actionable messages, structured logging
Deps	dependency-management	Stdlib-first, pinned versions, lock files
Files	file-hygiene	Proper .gitignore, no generated files committed
CI	ci-safety	Never skip tests, never modify CI without asking
Secrets	no-secrets	No credentials in code, env vars or secrets manager
Style	code-formatting	Use project's formatter, don't mix style with logic
Authoring	context-artifacts	Plugin structure, rule format, review iteration, surface sync, consistency checks
Authoring	skill-authoring	SKILL.md structure, step numbering, typed calls, tile.json reference
Authoring	script-delegation	Deterministic → script, reasoning → LLM, the regex trap
Authoring	plugin-evals	No bleeding, no leaking, persistent eval coverage

Skills

Skill	Description
release	PR creation, Copilot review, merge + cleanup workflow
eval-authoring	Generate, review, iterate on eval scenarios with score-driven feedback
install-reviewer	Scaffold a gh-aw PR review workflow into a consumer repo — reviews every PR against the latest published `jbaruch/coding-policy`

Philosophy

Language-agnostic code rules. The code quality rules (commits through formatting) apply to Python, TypeScript, Go, Rust, Java — any language. No framework-specific assumptions.
Tessl-specific authoring rules. The authoring rules (context-artifacts through plugin-evals) are specific to the Tessl plugin workflow. They codify how to build, test, and ship tiles.
One concern per rule. Each file covers one topic. Easy to read, easy to reference, easy to override if a project needs an exception.
Opinionated but practical. These rules reflect real patterns found across 17+ repositories and the Tessl plugin authoring workflow. They solve problems that actually come up when agents write and ship code.
Always on. Every rule is alwaysApply: true. Agents follow these conventions without being reminded.

Workspace: jbaruch
Visibility: Public
Created: 5 days ago
Last updated: about 3 hours ago
Publish Source: CLI
Badge