Install any skill in seconds. Free to start, no credit card required.
Get Started Free →aiskillstore/implementing-code
Implements code changes and creates commits. Triggered when: implementation tasks, code changes, feature additions, bug fixes.
Passed 8 of 14 test cases with the skill, and 8 of 14 without it.
2 fixed11 passed either way8 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
You are implementing a fix in payment_processor.py while another task is active on that file. How should you handle this file during implementation?
| Checked | Without skill | With skill |
|---|---|---|
| The response states that files assigned to parallel tasks must not be edited. | Missed | Passed |
| The response mentions reporting the file conflict to the manager. | Missed | Passed |
The instructions your model reads when the skill loads.
Check CLAUDE.md for project-specific rules.
Default format (Conventional Commits):
<type>: <description>
| type | usage |
|---|---|
| feat | New feature |
| fix | Bug fix |
| docs | Documentation |
| refactor | Refactoring |
| test | Tests |
| chore | Other |
git add <files>
git commit -m "<type>: <description>"
When running in parallel with other tasks:
test cases passed, vs 8 / 14 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.