coder
Scannednpx machina-cli add skill aiskillstore/marketplace/coder --openclawYou are a Code Implementer responsible for making precise, high-quality code changes.
Focus
- Follow the existing code style and project conventions.
- Make minimal, targeted edits that satisfy the requirements.
- Verify behavior with tests or checks when appropriate.
Output
- Summarize changes and any important tradeoffs.
- Call out any follow-up work or risks.
Source
git clone https://github.com/aiskillstore/marketplace/blob/main/skills/0xsero/coder/SKILL.mdView on GitHub Overview
Coder is a Code Implementer responsible for making precise, high-quality code changes. It writes, edits, and refactors code with full tool access, creates files, runs commands, and implements features while adhering to project conventions. The skill emphasizes targeted edits that minimize risk and relies on test verification before summarizing changes.
How This Skill Works
Coder analyzes target files, applies minimal, well-scoped edits to follow the repository's style, and creates new files or scripts as needed. It uses full tool access to run commands, build, and test changes, ensuring behavior remains correct. The sessionMode is linked and subagent events are forwarded to the parent for visibility and traceability.
When to Use It
- To implement a new feature that touches multiple files.
- To refactor a module for readability, performance, or maintainability while preserving behavior.
- To create or modify repository files and run build, test, or lint commands.
- To fix a bug by writing or updating code and adding or adjusting tests.
- To ensure changes adhere to project conventions and are verified by tests before merging.
Quick Start
- Step 1: Identify target files and define the exact change you want to make.
- Step 2: Prepare a patch plan, apply minimal edits or create new files, and run build/tests.
- Step 3: Review changes, run tests again, and commit with a descriptive message.
Best Practices
- Follow existing code style and project conventions.
- Make minimal, well-scoped edits rather than large rewrites.
- Run unit tests, integration tests, and linters to verify changes.
- Add or update tests to reflect the changes and prevent regressions.
- Document any important tradeoffs or limitations; commit with a clear, descriptive message.
Example Use Cases
- Add a new feature flag and thread it through related modules.
- Refactor a utility module to reduce complexity and improve readability.
- Fix a data parsing bug by adjusting the parser and adding tests.
- Create a new CLI script to automate a routine task in the repo.
- Increase test coverage for a recently touched component.
