Files
redsen-lean-harness/templates/conventions.md
T
mozempkandCopilot 383129f571 feat: scaffold redsen-lean-harness v0.1.0
Recovered from crashed session (Node OOM). Repo contains full P0-P6
scaffold: plugin.json/marketplace.json, AGENTS.md, ADRs 0001-0006,
lh CLI (init/index/graph/lane/run/memory/host/report/doctor), 10
.github/agents, 12 CLI skills, instructions, context7 mcp.json, and
unit/e2e test suite.

Fixed: run.mjs read --in-tokens/--out-tokens but tests and CLI docs
use --input-tokens/--output-tokens, so telemetry totals were always 0.
Now accepts both forms.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
2026-09-09 22:44:15 +02:00

930 B

{{PROJECT}} conventions

Code style

  • Prefer simple control flow and explicit names.
  • Keep side effects at boundaries.

Naming

  • Use domain terms consistently.
  • Name files after their primary responsibility.

Testing

  • Cover changed behaviour with the smallest meaningful test.
  • Add regression tests for fixed bugs.

Error handling

  • Fail fast on invalid inputs.
  • Preserve actionable error context without leaking secrets.

Commit format

  • Use concise conventional commits when possible.
  • Explain why in the body when not obvious.

Directory layout

  • Keep generated artifacts out of source directories.
  • Put shared deterministic helpers in library modules.

Review rules

  • Verify scoped files only.
  • Flag correctness, security, and contract drift before style.