close-step
/close-step
Domyka krok: doprowadza lokalne CI do zieleni, zamyka uwagi, uzupełnia śledzenie, aktualizuje plik stanu i tworzy lokalny commit.
- Repozytorium
- you-decide ↗
- Licencja
- Apache-2.0
- Ostatnia zmiana repozytorium
- 07.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 07.11.2026, bez odwołań do wycofanych modeli i API.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
Co robi i kiedy
Domyka krok: doprowadza lokalne CI do zieleni, zamyka uwagi, uzupełnia śledzenie, aktualizuje plik stanu i tworzy lokalny commit.
Wyzwalacze z opisu
Oryginalny opis (EN)
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".
Jak działa
- 1. Local CI
- 2. Findings of the step (standard and strict levels)
- 3. Traceability and AI usage (strict level)
- 4. State
- 4 bis. Memory (standard and strict)
- 5. Local commit
- 5 bis. After the commit (standard and strict, if the owner enabled them)
- 6. Report
Podgląd SKILL.md
--- 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`).
Wersje
W bazie nie ma innych skilli o nazwie close-step.
Migawka bazy z 13.11.2026 · wersja paczki e42a8801b476 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100close
Zamyka krok po /check: przegląd kodu, pełne testy, migracje i lint, a potem uzupełnia ślad zgodności. - 100finish-task
Przeprowadza gotowe zadanie przez uproszczenie, przegląd, ocenę, commit i pull request w tej kolejności. - 100finish-work-on-local-worktree
Zamyka worktree: scala gałąź lokalnie do main, aktualizuje status dokumentacji i plan projektu oraz rekomenduje kolejny kamień milowy. - 86done
Zamyka zadanie programistyczne: sprawdza, czy jest gotowe, i przygotowuje je do przekazania albo zamknięcia. - 100dx-step
Wykonuje następny oczekujący krok z implement.md: implementacja, testy, przegląd, commit i aktualizacja statusu, po jednym kroku naraz. - 100pensieve-wrap-up
Domyka otwarte wątki pracy w Pensieve przez wypchnięcie lub odrzucenie zmian oraz kroki w git, GitHubie i systemie zgłoszeń.