AI coding tools
Jules Operating Card
Use Jules for reviewed GitHub tasks in an isolated environment with repository-specific setup, plan approval, and branch evidence.
- Format
- Reference
- Level
- Beginner
- Audience
- Practitioner, Developer
- Owner
- Project42 Editorial
- Review cadence
- Every 30 days
- Prerequisites
- An approved Google account; A GitHub repository connection; A reviewable target branch
Use it for plan-first isolated repository work
Jules connects to selected GitHub repositories, prepares a virtual-machine environment, and generates a plan before changing code. Choose it for a specific bug, documentation task, test, or feature that has an observable result.
Connect only the required repositories and select the intended branch. Keep AGENTS.md and environment setup current so the plan reflects the actual build and test process.
Review the plan and environment before execution
Write a narrow task, add only necessary setup, and inspect the proposed plan before approval. Avoid placing credentials in setup scripts or prompts; use only the product's approved secret path when a task truly needs one.
Review the resulting diff and run the repository's checks independently before accepting or merging changes.
Task: [one GitHub outcome]
Scope: [repository, branch, and allowed paths]
Permissions: [repo connection, network, and environment]
Setup: [reproducible non-secret preparation]
Plan gate: [what must be reviewed before execution]
Verification: [diff, checks, and merge review]
Recovery: [stop task, discard branch, restore environment]Expected evidence and verification
Expected evidence includes repository and branch selection, task prompt, environment setup, approved plan, produced diff, and test results. Verify the actual branch rather than relying only on the session summary.
When the environment or plan is wrong, stop before mutation, correct the setup or AGENTS.md guidance, and submit a narrower task. Discard isolated changes that cannot be verified.