Ship code through GitHub

Configure GitHub access

1. 1
   Enable GitHub

   Connect a GitHub App or token through Home → Integrations.

2. 2
   List write repositories

   Reads may be broader, but pushes and mutating API calls are limited to repositories the operator explicitly adds.

3. 3
   Choose the main-branch rule

   Keep direct pushes to protected branches blocked and require approval for held pushes when the workflow needs it.

4. 4
   Add repository guidance

   Use AGENTS.md for tests, ownership, branch, and review conventions.

The prompt to send

Ask for the outcome and the standard it has to meet, including how far to go on its own. Most of the value is in stating where the work stops.

In the billing service, add support for annual plans alongside the monthly
ones, including the proration when someone switches mid-term.

Read the surrounding code first and match its conventions.
Work on a focused branch and leave unrelated changes alone.
Add tests in proportion to the risk, and run the suite before you push.
Open a pull request describing what changed and why.
Stop before merging and tell me what you could not verify.

What you check afterwards

• Read the diff rather than the summary of the diff.
• Confirm the branch is the one you expected and that unrelated files were not swept in.
• Check Tool audit for the pushes and API calls made, and approve or deny anything held at the boundary.