Skip to content
Back to skills

Implement

ASecurity

Implement one issue, from reading it to the commit.

  • 5 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 6, 2026
code-qualitygocode-reviewgit

Security analysis

A100/100

Scanned October 6, 2026

npx -y skills add aaronmallen/aaronmallen.me --skill implement --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Implement?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Implement
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aaronmallen-implement/badge)](https://www.skillsdirectory.com/skills/aaronmallen-implement)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
description: Implement one issue, from reading it to the commit.
name: implement
---

# Implement

Take one issue from open to committed.

## 1. Read the issue

Issues live on GitHub. Work from [`.claude/issues.md`][issues] for every command and label here.

Read the issue by its number.

Read the story for the why and the criteria for the what. Every criterion has to hold when you are done.

Read the code the issue touches before you change any of it. Read the tests too. A test name states the intent,
so read it before you call any behaviour a bug.

Then add the `in progress` label.

## 2. Write the code

Read `.claude/CLAUDE.md`, the README and the records in `docs/adr` that cover the area. Then:

- **The tests are the contract.** A failing test means the code is wrong. Change a test only when the issue asks
  for the behaviour to change.
- **Write tests for what you add**, covering the behaviour and the edges.
- **Follow what is already there.** A new file looks like the files beside it.
- **Change only what the issue names.** Anything else you spot goes to the user, not into the diff.

When the issue is the record for a decision, invoke `/write-adr` and stop there. The record lands in its own
commit, under the code that carries it out. That commit says `See #<issue>`, and the code on top closes it.

## 3. Check it

```sh
mise run format
mise run lint
mise run test
```

All three pass before you go on. Run the whole lint, not one language.

## 4. Review it

Invoke `/code-review`. Fix what it finds, or say why a finding stands.

## 5. Commit

Find the parent spec, if the issue has one, and read its sub-issues. When every other sub-issue is closed or in
`needs review`, this issue's last commit closes the spec too.

Invoke `/commit` with the issue number, whether this is the issue's last commit, and the spec when this commit
closes it. Do not close the issue or the spec with `gh`. The commit closes them when the owner pushes.

## 6. Hand it over

Swap `in progress` for `needs review` on the issue. Then read the issues it blocks, and take `blocked` off each
one whose blockers are all closed or in `needs review`.

If a step failed and you could not fix it, leave the issue `in progress` and tell the user what stopped you. Do
not mark work done that is not.

[issues]: .claude/issues.md

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…