Overview

The implementing-code skill automates targeted code modifications guided by existing project patterns. It locates target files with Glob, inspects references with Grep, applies changes via Read/Write/Edit, and commits using a conventional format. It respects project-wide rules defined in CLAUDE.md and reports a completion summary including changed files and the resulting commit hash.

How This Skill Works

You leverage Glob to identify target files and Grep to inspect references, then implement changes that follow the repository’s established patterns using Read/Write/Edit capabilities. After changes are made, you stage and commit them with git using a conventional type (feat, fix, etc.). The skill outputs a Completion Report that lists changed files, a concise implementation summary, and the commit hash.

When to Use It

• Implementing a new feature that touches multiple files or modules
• Applying bug fixes discovered during issue triage
• Performing a safe refactor that requires updating call sites or internal helpers
• Aligning code with new API changes or deprecated behavior
• Automating code maintenance tasks that must be version-controlled and auditable

Quick Start

1. Identify the target files using Glob patterns tied to the task input.
2. Make code changes following existing project patterns with Read/Write/Edit tooling.
3. Stage and commit changes using git with a conventional message (e.g., feat:, fix:).
4. Review the Completion Report for changed files, implementation summary, and commit hash.

Best Practices

• Always consult CLAUDE.md for project-specific commit rules and any task-specific constraints.
• Keep commits small and focused on a single logical change; avoid large, multi-purpose commits.
• Validate that changes align with existing coding standards, tests, and patterns before committing.
• If you need to modify multiple files, coordinate to avoid editing the same files in parallel; report any conflicts to the manager.
• Update or add tests when introducing new behavior or fixing bugs to maintain test coverage.

Example Use Cases

• feat: add feature-flag support across modules and wire through orchestrator
• fix: correct off-by-one bug in loop and update dependent call sites
• refactor: rename internal helper across files to adhere to naming conventions
• feat: introduce batch processing API and integrate into scheduler
• test: add unit tests for new utility function and edge cases

Frequently Asked Questions