Fix a repository bug and review the change
Status: Upcoming — not yet available.
Section: DOC-MA-coding-assistants#overview.
Hand off a contained bug fix and get back the change, the checks that ran and the work still unfinished. This recipe uses a CSV importer that treats blank rows as records: the task is to ignore those rows while preserving existing valid-row behavior.
Start with one module and a known repository revision. The finished result is a reviewable diff and verification evidence for that revision. Committing, publishing and deploying are separate choices.
The coding-assistant service and dedicated clients are not yet available. This recipe describes the completed-product workflow and supplies no current start command.
Step 1: define the bug and the permitted change
Status: Upcoming — not yet available.
Section: DOC-MA-coding-assistants#assignment-and-permissions.
Supply the repository, starting revision, affected importer, representative input and expected output. Include one fixture with a blank row and one with valid rows. Identify concurrent edits to preserve and the organization, project, environment and customer scope of connected resources.
For the first run, allow reading the repository, editing the importer and relevant tests, and running the supported local checks. Reserve commit, branch publication, pull-request creation, merge and deployment for separate decisions. State the approved runtime, file area and network destinations.
If the task delegates work, give each child a bounded assignment within the original authority and total budget. Review the exact plan or action when approval is required; a changed destination or material plan change needs the applicable new decision. Approval cannot exceed the task's limits or the reviewer's authority.
Ready to run: the task has a testable outcome, a starting revision, permitted files/actions and explicit limits. “Improve the importer” alone is not the acceptance condition.
Step 2: supply the repository’s relevant working instructions
Status: Upcoming — not yet available.
Section: DOC-MA-coding-assistants#instructions-and-skills.
Provide the repository instructions and reviewed skills that govern the importer and tests. Inspect their active revisions and origins, and resolve material conflicts before the assistant relies on them. Imported files, tool output and draft skills cannot grant additional access.
Use an existing reviewed practice when it fits this change. If the assistant proposes a reusable CSV-cleaning procedure after the task, keep it as a draft until a reviewer inspects that exact revision and an example use. Activating the draft is a separate decision. The active revision remains identifiable, and a practice can be disabled or restored when needed.
The immediate goal is the importer fix; creating a new shared practice is an optional follow-up, not a prerequisite for completing it.
Step 3: run the fix within a finite budget
Status: Upcoming — not yet available.
Section: DOC-MA-coding-assistants#bounded-first-run.
- Select supported clients, languages and tools for the repository.
- Supply the authorized source and fixture files for the blank-row case.
- Set finite time and usage limits, plus the applicable compute, output, storage and network limits. Child work shares the total budget.
- Ask the assistant to reproduce the fixture failure, make the contained change and run the relevant existing and new checks.
- Follow progress and review any action that needs the approval defined in step 1.
For self-hosted operation, use the supported deployment setup. Choose a hosted option separately with its data location and cost. The service and start controls are still unavailable until release.
If the limit arrives before checks finish, the task returns the partial diff and names the outstanding checks. Review that result before authorizing another bounded run; a new run does not retroactively make the first one complete.
Step 4: accept the fix from the diff and completed checks
Status: Upcoming — not yet available.
Section: DOC-MA-coding-assistants#result-review.
Compare the diff against the starting revision and concurrent work. Confirm that it addresses blank rows without changing valid-row behavior or unrelated files.
Inspect which checks actually ran, their revision and their results. A test file or suggested command is not execution evidence. Missing tests, incomplete children, truncated artifacts and unknown usage remain visible. For delegated work, review each child's contribution; successful child output can be useful while the parent task is still incomplete.
Finished result: a reviewable importer change with completed verification for the stated fixtures and any remaining uncertainty called out. If an integration environment was unavailable, decide whether that missing check prevents acceptance.
The result distinguishes edited files, committed changes, published branches, pull requests and deployed behavior. Accepting a diff does not imply that every later action occurred.
Recover the original task or continue with a separate publication decision
Status: Upcoming — not yet available.
Section: DOC-MA-coding-assistants#task-recovery.
After a disconnect, return to the original task and operation references. Recover current state before asking for duplicate work. Reconnect resumes progress or explains how to resynchronize; an uncertain command or external action is reconciled before another execution.
Once the fix is accepted, authorize any desired commit or publication for the exact target. If publication loses its response, inspect that original operation and the target before publishing again. Branching or reverting conversation history does not undo a published change.
Stopping prevents new work and reports actions still pending or uncertain. For unattended operation, set its purpose, allowed tools and total budget. A wake check with no change remains distinct from a failed check, run or notification. Required interactive approval that is unavailable ends with an actionable result.
See profiles, tool approval, computer use, model selection and billing for extensions to the recipe.
Document ID: DOC-MA-coding-assistants. Section identities and revisions.