CtrlK
BlogDocsLog inGet started
Tessl Logo

jbaruch/context-workshop

Decomposed ticket workflow from the AI Native DevCon London 2026 context workshop: skills for code and documentation tickets, the mandatory tests-first / clean-review / human-review rules, and the deterministic scripts/ they lean on.

70

Quality

88%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

tests-first.mdrules/

Rule: no tests, no PR

Scope: any ticket that touches source code (the code-ticket workflow).

A project with no tests gives a code change nothing to stand on. Therefore:

  • Before implementing a code ticket, you MUST run the deterministic gate: python3 scripts/run_tests.py --check.
  • If it exits non-zero (no test runner detected), you MUST NOT implement the change and MUST NOT open a PR. Write tests first, then re-run the gate.
  • You MUST NOT rationalise around this ("it's a tiny change", "I'll add tests later"). No tests means no PR, full stop.

The check is mechanical and lives in scripts/run_tests.py (--check); this rule is the obligation to honour its exit code.

README.md

tile.json