--- name: do-code-687873ebe29b description: Implement a focused code change. Use this skill as the wrapper for any implementation work so the Maverick workflow report captures what was done and so the agent applies the project's coding standards before editing. Intended to be invoked once per task from inside a do-issue-* or do-epic phase, not standalone. argument-hint: brief description of the task (one line) user-invocable: true disable-model-invocation: false --- # Implement a Code Change Wraps implementation work in a Maverick skill so the workflow report records what was done and the agent applies the project's coding standards before editing. Invoke this skill **once per task** from inside `do-issue-solo` / `do-issue-guided` / `do-epic` Phase 5. The argument is a one-line task description that gets logged in the report. This skill is a thin wrapper. The actual edits are made by the orchestrating Claude Code session using its built-in tools (Read, Edit, Write, Bash, Grep). The skill's job is to pin standards and scope, not to perform the edits in a subagent. ## Project rules (mandatory) Before doing anything else, check for repo-specific coding guidance at `docs/maverick/skills/do-code/SKILL.md` (path relative to the repo root). - **If the file exists**, read it fully and treat its contents as binding for this task. It holds project-specific rules that all Maverick coding in this repo must follow. Where it conflicts with generic guidance below, the project file wins. - **If the file is absent**, continue without it. Do not create or scaffold the file as part of this task. ## Preflight (mandatory) Run this **first**. If it exits non-zero, halt and report the stderr output to the user verbatim. Do not proceed. ```bash uv run maverick preflight do-code ``` Skip the preflight when invoked from inside a `do-issue-*` or `do-epic` phase — the orchestrator already ran a stricter one this session. Run it only when this skill is invoked standalone. The check verifies the project is initialised and `uv` is on PATH. ## Standards to apply Before editing, read and follow: - `mav-scope-boundaries` — implement only what `$ARGUMENTS` asks for. No unrelated cleanup, no opportunistic refactors, no abstractions for hypothetical future requirements. Three similar lines is better than a premature abstraction. - `mav-bp-error-handling` — error handling at system boundaries only (user input, external APIs). Don't catch what framework guarantees rule out. No defensive code for scenarios that can't happen. - `mav-bp-operability` — log levels, structured fields, and the project's logging conventions. - `mav-bp-application-security` — input validation, secret handling, authn/authz patterns. If the change touches any of these, surface the design choice in your verification. Also read **any project-level skills** at `docs/maverick/skills/` — topic-specific guidance for this codebase that supplements the maverick-wide best practices. ## Implementation loop 1. **Read before writing.** Open the files you're about to change. Grep for existing patterns nearby — the goal is for the edit to look like it was written by whoever wrote the surrounding code. 2. **Make the change.** Smallest diff that satisfies the task. If you notice an unrelated bug or a tempting refactor, **do not fix it** in this skill — write it down for a follow-up. 3. **Verify** per `mav-local-verification` (lint, typecheck, tests). Run the project's verification commands. 4. **If verification fails**, diagnose per `mav-systematic-debugging` and fix. Do not paper over a failing test or silence a lint warning. Do not commit red. 5. **Return** when (a) the task is done and (b) verification is green. ## Rules - **Default to no comments.** Identifiers carry the WHAT. Only add a comment when the WHY is non-obvious (hidden constraint, subtle invariant, workaround for a specific bug). No "removed X" / "added Y" / "used by Z" comments — those rot. - **No half-finished implementations.** If the task can't be completed cleanly, halt and report rather than leaving partial state. - **No unauthorised destructive actions.** Don't `git push --force`, `git reset --hard`, `rm -rf`, drop tables, or delete data. If the task description doesn't explicitly authorise a destructive step, treat it as out of scope and ask. - **Tests are part of the change.** If the change is testable, write or update tests in the same task (or wrap that work in `do-test` as a sibling call before the commit). - **Stay inside the task envelope.** When `$ARGUMENTS` is ambiguous, ask for clarification rather than guess. ## Return Protocol `do-code` is a **subroutine of the calling workflow's per-task loop** — not a terminal action. Returning from this skill is a hand-back to the caller's next numbered step, not a completion event (#106). When you return from this skill, **do not** post a closing summary, do not stop, do not treat verification-green as "task done." The calling workflow's loop still owns, in order: 1. Closing the `skill-dispatch` interval that wrapped this invocation (`uv run maverick report end skill-dispatch … --outcome success`). 2. Optionally sibling-calling `do-test` for tests that weren't folded into this skill. 3. Conventional commit referencing the issue number, then push (with stacked-PR retarget if applicable). 4. Logging the commit row to the workflow report (`uv run maverick report commit …`). 5. Updating the tasks comment / closing the sub-issue. 6. Heartbeat refresh. If you find yourself drafting a final summary after returning here, that is the signal: scroll back to the calling workflow's per-task loop and resume from the step immediately after the `/do-code` invocation. --- Source attribution: thermiteau Original project: https://github.com/thermiteau/maverick/blob/2c4bdc1df54b2e3bd5e2ed059c457854fb435be0/skills/do-code/SKILL.md License: Apache-2.0 License information: https://www.apache.org/licenses/LICENSE-2.0 Original upstream instructions; downloaded from Mega AI Hub. ## Upstream license notice Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright [yyyy] [name of copyright owner] Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. # Mega AI Hub resource metadata Creator / publisher: thermiteau Original project: https://github.com/thermiteau/maverick/blob/2c4bdc1df54b2e3bd5e2ed059c457854fb435be0/skills/do-code/SKILL.md Attribution basis: Source repository record Fields of work: Development & Engineering Roles: Backend Developer, DevOps / SRE, Full-Stack Developer Specialties: API, Design, Frontend, Git, Mobile, Testing Tools: Maverick Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: 63413700ef6ac0fae5ad38300ada468ce70754e8d0ed7bc76a09beccba6bb61b