This repository defines instructions for generic coding agents and specifically Jules regarding conventions, CI tasks, and project rules.
When Jules parses this repository in response to an automated scheduled task or PR review, it must adhere to these directives:
If you are operating as part of a recurring "Scheduled Task", your goal is full codebase validation:
- You MUST run
python check_gh_jules.pyto assert GitHub integration state. - If fixing bugs, verify changes by ensuring tests pass before concluding the session.
If you are invoked to review a PR (e.g., triggered by jules:review or jules:test labels):
- For
jules:review: Read the diff and provide actionable, inline feedback pointing out logical errors, potential data leaks, or unoptimized complexity. Do NOT hallucinate dependencies. - For
jules:test: Immediately write accompanying tests for all untested classes introduced in the PR, and push the branch. Ensure tests pass before completion.
All agents working on this project (especially Jules in autonomous mode) MUST adhere to the GSD execution framework:
- State Initialization: Every session MUST begin by reading
.planning/ROADMAP.mdto understand the current milestone and phase targets. - Context Loading: Read the
CONTEXT.mdof the active phase to ingest research and background knowledge. - Mandatory Planning: For any task involving structural changes or new features, a
PLAN.mdMUST be created (or followed if already present) before code modifications. - Proof of Implementation: Update the relevant phase
SUMMARY.mdwith a detailed list of changes made during the turn. - Verified Completion: Run automated tests for all logic changes. A task is not complete until a
VERIFICATION.mdfile is generated documenting passing tests and manual verification steps. - Roadmap Sync: Upon conclusion of a phase, update
ROADMAP.mdby marking the corresponding items as completed ([x]).