dj-library-tools

Short-lived feature branches; TDD + lint + merge-ready command as exit criteria before commit; push and merge to main (or user-directed flow). Do not default to asking the user to open a PR. Use when implementing a feature or non-trivial fix, when the user asks for branch/git workflow, or after substantial edits that should not stay uncommitted.

Change-aware quality pass: diff scope, readability, function size and control flow, comments where non-obvious, and alignment with project linting. Use before merge or with handoff when the user wants industry-style maintainability beyond what tests assert.

Define and maintain lightweight evaluations (acceptance criteria, regression checks, golden tests) so “green” is objective and repeatable.

Evidence-driven debugging/incident workflow: reproduce, isolate, minimize, fix, verify, and prevent regressions.

Establish lightweight release discipline: definition of merge-ready, versioning/changelog habits, and safe rollout/rollback practices.

Maintain a lightweight risk register (top risks, triggers, mitigations, rollback) to prevent scope drift and improve decision quality.

Lightweight security review for agent work: secrets hygiene, safe logging, least privilege, and threat-model-lite checks.

Match UI graphics to reference examples (examples/ screenshots and specs). Use when drawing or changing visuals so the result matches the examples without back-and-forth.

Review code changes for correctness, security, project conventions, and maintainability. Use when reviewing a diff, before commit, or when the user asks for a code review.

Receiving-agent protocol. Boots a new agent into the minimum correct context (select + isolate) and produces a clear next-step plan without guessing.

Operating model for disciplined agent work: stay on scope, avoid guessing, decompose work into verifiable chunks, and keep context lean and durable.

Leaving-agent protocol. Produces a compressed, decision-first handoff that preserves intent and next steps while stripping execution noise.

Black-box tests, test-first for core logic, and continuous test runs. Use when adding or changing tests or app logic. Run your project’s test command after changes; keep suite green.