Skip to content
Skills Library
Programming · Building & coding

close-step

/close-step

Closes a step or task. Gets the local CI green, closes the step's findings, logs traceability and AI usage, updates the state file, makes a local commit and sends a short report to the owner. Use when a step's code is written and tested, or when the user says "commit", "close the step", "wrap up", "finish".

Repository
you-decide ↗
Licence
Apache-2.0
Last repository change
07.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 07.11.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Closes a step or task. Gets the local CI green, closes the step's findings, logs traceability and AI usage, updates the state file, makes a local commit and sends a short report to the owner. Use when a step's code is written and tested, or when the user says "commit", "close the step", "wrap up", "finish".

Triggers from the description

s code is written and tested, or when the user saysclose the stepwrap upfinish
Original author description

Closes a step or task. Gets the local CI green, closes the step's findings, logs traceability and AI usage, updates the state file, makes a local commit and sends a short report to the owner. Use when a step's code is written and tested, or when the user says "commit", "close the step", "wrap up", "finish".

How it works

  1. 1. Local CI
  2. 2. Findings of the step (standard and strict levels)
  3. 3. Traceability and AI usage (strict level)
  4. 4. State
  5. 4 bis. Memory (standard and strict)
  6. 5. Local commit
  7. 5 bis. After the commit (standard and strict, if the owner enabled them)
  8. 6. Report
Original SKILL.md headings · 44 lines, 449 words
SKILL.md preview
---
name: close-step
description: Closes a step or task. Gets the local CI green, closes the step's findings, logs traceability and AI usage, updates the state file, makes a local commit and sends a short report to the owner. Use when a step's code is written and tested, or when the user says "commit", "close the step", "wrap up", "finish".
---

# Close a step

## 1. Local CI
Run the CI command written in CLAUDE.md, offline by default. On failure, fix the cause: never disable a check, never
add a lint suppression to make it pass. Read only the last lines of the output.
If the build output folder grows large, say so in the report and propose cleaning it; never delete it without the
owner's yes.

## 2. Findings of the step (standard and strict levels)
Grep the open findings that target this step in `docs/findings_log.md`. All are fixed and closed before the commit,
or moved to the sub-step that writes the code they depend on, with the reason written. **No step closes on an open
finding.** If no review was done for this step, run the `review` skill first.

## 3. Traceability and AI usage (strict level)
- One row per covered criterion in `docs/traceability.csv` (format in `story-to-tests`).
- One row appended to `docs/ai_usage.md` **without reading the file**:
  `| date | tool and model; what was verified (build, lint, tests, human review) | files | contribution | human decision or change | follow-up |`

## 4. State
Update `docs/state.md`: current step, the next three actions, what the owner must decide, and a dated entry at the
top of its update log. Keep it under 150 lines; whatever leaves it must already be written elsewhere (plan, logs,
decisions).

## 4 bis. Memory (standard and strict)
Run the `memory` skill's commands before the commit: `move`, `map`, `guard --update` (a loss is declared with
`--accept "reason"`, never in silence), then `check`. Commit `docs/memory/` with the step.

## 5. Local commit
- Commit convention from CLAUDE.md; body in factual bullets; findings cited by id; trailers as configured
  (for example `AI-Assisted: yes`, and `Signed-off-by` through `git commit -s`).
- `git add` only the step's files: never scratch files, build output, secrets or real data.
- Write the message to a UTF-8 file and run `git commit -F <file>`. Check with `git log -1 --format=%s`.
- Windows scripts: never name a PowerShell function like an alias (`erase`, `del`, `rm`, `ls`, `cat`…: the alias wins),
  and never run a command that can wait for a confirmation in a hidden window.
- **Never push** without the owner's explicit "yes" at that moment. Never `--amend`, `reset` or `rebase` without them.

## 5 bis. After the commit (standard and strict, if the owner enabled them)
The `memory` skill's `journal --all`, then `sync` for the claude.ai Project copy (it reads the commit just made).

## 6. Report
Short: what is done, the path of every created or modified file, the CI result, what the owner must decide.
Standard and strict levels: tick the request in `docs/requests_log.md` (skill `log`).

Versions

The database has no other skills named close-step.

Database snapshot: 13.11.2026 · package version e42a8801b476 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100close
    Closes the current step (<feature>-step-<n>) after /check. Runs /audit self (code review, fixes, "Code review" section) unless its last round has the same fingerprint, reruns the full suite, migrations, lint and type check only if the step's fingerprint changed since /check…
  • 100finish-task
    Use when implementation is done and the task is ready to commit and PR. Runs simplify → review → score → commit → PR in sequence. Triggers on "finish task", "ready to PR", "wrap up", "close out", "done implementing", "submit PR".
  • 100finish-work-on-local-worktree
    This skill should be used when the user says "finish worktree", "close out worktree", "merge and close milestone", "finish this worktree", "done with worktree", "wrap up worktree", or when a worktree branch is complete and needs to be merged into main AND related documentation…
  • 86done
    Close a coding task. Use it when the person says the task is done, asks to wrap up or close it, or before delivering a medium or large task.
  • 100dx-step
    Execute the next pending step in implement.md — implement, test, review, commit, update status. Use to go one step at a time ('next step').
  • 100pensieve-wrap-up
    Close out the user's open threads with Pensieve, by shipping or discarding their work. Gets the threads closest to done and does the steps that close each one in git, GitHub and the issue tracker. Use when the user asks to wrap up, ship, close out, tidy, discard or finish their…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.