General-purpose coding policy for Baruch's AI agents
90
91%
Does it follow best practices?
Impact
90%
1.30xAverage score across 18 eval scenarios
Advisory
Suggest reviewing before use
A small team maintains a Tessl plugin that ships coding rules to their AI agents. One of their existing rules, pr-template-checklist, is currently marked to apply across every context. After several months of using it, the team realizes the rule only meaningfully fires when contributors are authoring or editing pull-request-related artifacts — PR description templates, contributor guides, the PR body itself when reviewing a draft. Outside of that context the rule has nothing to say, and surfacing it in every conversation is noise. Convert the rule from a universal rule into a conditional rule scoped to PR-related artifacts.
Modify rules/pr-template-checklist.md — update its frontmatter so the rule fires only on PR-related artifacts. Leave the rule body content unchanged.
The following files are the current state of the plugin. Extract them before beginning.
=============== FILE: inputs/.tessl-plugin/plugin.json =============== { "name": "acme/coding-rules", "version": "0.5.0", "description": "Acme's coding rules for AI agents", "private": false, "rules": [ "rules/commit-conventions.md", "rules/pr-template-checklist.md" ] }
.github/PULL_REQUEST_TEMPLATE.md or .github/PULL_REQUEST_TEMPLATE/*.md.tessl-plugin
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
scenario-10
scenario-11
scenario-12
scenario-13
scenario-14
scenario-15
scenario-16
scenario-17
scenario-18
rules
skills
adopt-fork-pr
eval-curation
install-reviewer