by DevOtts
One door for every Claude Code session close — ship pipeline (test gate → deploy → prod gate) + close core (debrief, ledger, sweep, honest verdict). The conclude stage of the *-it lifecycle.
# Add to your Claude Code skills
git clone https://github.com/DevOtts/conclude-itconclude-it is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by DevOtts. One door for every Claude Code session close — ship pipeline (test gate → deploy → prod gate) + close core (debrief, ledger, sweep, honest verdict). The conclude stage of the *-it lifecycle. It has 0 GitHub stars.
conclude-it's catalog security scan is still queued. You can run an instant dependency and prompt-injection check now with the "Scan for vulnerabilities" button above.
Clone the repository with "git clone https://github.com/DevOtts/conclude-it" and add it to your Claude Code skills directory (see the Installation section above). conclude-it ships a SKILL.md manifest, so compatible agents can discover and load it automatically.
conclude-it is primarily written in HTML. It is open-source under DevOtts on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh conclude-it against similar tools.
No comments yet. Be the first to share your thoughts!
Unlocks once the catalog security scan passes (runs nightly).
⚠️ Third-Party Software Notice
This skill is third-party open-source software developed and hosted independently on GitHub. SkillsLLM is an informational directory and does not control or maintain the underlying repository.
Any security checks, ratings, or warnings displayed by SkillsLLM are automated and limited in scope. They do not constitute a security certification or guarantee that the software is safe, error-free, or free from malicious code, vulnerabilities, compromised dependencies, or prompt-injection risks.
Review the source code, permissions, dependencies, and configuration before installing or running any third-party skill. Use is at your own risk. To the maximum extent permitted by applicable law, SkillsLLM is not liable for losses arising from third-party software.
The deep catalog scan for this skill is still queued. Run an instant dependency check now instead.
/plan-it plans it, /build-it builds it, /review-it reviews it,
/conclude-it concludes it — whether "it" is a shipped epic or an ordinary
working session. Closing a long session without a ritual leaves debris: knowledge
that lived only in the conversation is lost, background jobs keep running,
unmerged work is stranded, finished subagents linger as RAM-holding zombies —
and, worst, features get filed as "done" that were never proven in prod. This
skill sequences the close so none of that survives it.
First run in a repo: a five-question setup interview (docs home, second brain + scope, deploy skill, debrief skill) — answered once, saved inside the repo, asked again only in a repo without the block. See the setup section below.
One command, two legs. Step 0 triages mechanically; the user never chooses:
Before the first close in a repo, resolve five facts. They are per-repo
memory, saved inside the repo — never global unless the user says so. Look
for the block ## conclude-it — project setup in CLAUDE.md → AGENTS.md →
.conclude-it/config.md; found (or derivable from existing agent
instructions) → use silently. Missing → detect first (candidate docs
folders, *deploy*/*debrief* skills, vault signals), then ask ONE batch of
five questions, each pre-filled with what detection found:
<project>-deploy skill with this repo's exact instructions and
I'll follow it every ship." Record the skill, or none + the
recommendation; offer to scaffold it now.<project>-debrief skill that
explains how your documentation structure works and I'll follow those
guidelines." Record it; else the generic debrief flow.Write the answers into the repo (the file it already uses — CLAUDE.md, else
AGENTS.md, else create CLAUDE.md):
## conclude-it — project setup
- docs_home: docs/
- second_brain: ~/Vault/MyBrain # or: none
- second_brain_scope: global # global | per-project | none
- second_brain_notes: session knowledge → wiki/projects/<slug>/ (guessed — confirm)
- deploy_skill: acme-deploy # or: none (recommended: create acme-deploy)
- debrief_skill: acme-debrief # or: generic
- configured: YYYY-MM-DD
If the user explicitly says "save this globally", ALSO write the answers as
user-level defaults; per-repo blocks always override. Consumers: the debrief
step runs debrief_skill against docs_home; the ledger card mirrors to the
second brain only when its scope says global; the ship pipeline deploys via
deploy_skill — none values degrade inline and the verdict repeats the
create-a-skill recommendation once.
Fail-closed, in order. (The Claude Code plugin carries an expanded version in
references/ship-pipeline.md, loaded only when triage says ship-shaped; this
file is self-contained — on any other agent, run the steps below as written.)
done-<name>./iterate
until green; a red local gate never proceeds to prod. No runnable suite? say
"unverified", don't manufacture a pass.git mv the epic's plan docs to their home's 0-done/
sibling; fix links.status: deprecated — never
two "current" docs describing two versions of the same feature.<repo>/.agents/history/ + INDEX row;
every session gets one, so "which session did X?" stays answerable for ~150
tokens instead of a transcript distillation.build-report.py + template:
light/dark toggle, badge cards, per-item "How to test" blocks, embedded
markdown reports). RED/UNVERIFIED items get their own badge — a report that
only shows the green half is a fake.This file is the complete, self-contained ritual: it runs on any SKILL.md-compatible agent (Cursor, Codex CLI, Copilot, OpenCode, Windsurf, Gemini CLI, and 70+ others via the Agent Skills standard). Some helpers it names are Claude Code plugin pieces; when one is absent, degrade inline and say so — never skip the step and never pretend the helper ran:
/iterate / /full-qa absent → run the diagnose→fix→re-test loop and
the e2e/smoke verification yourself, inline. The gates and their fail-closed
rules are unchanged.build-report.py + template ship only in the
plugin) → write CONCLUDE_REPORT.md (markdown) with the identical structure:
gates scoreboard first, per-item sections with status + "How to test" steps,
RED/UNVERIFIED first-class.session-debrief absent and the project has no debrief skill →
capture inline: dated session-log entry in the project's docs + the
promotion/supersession sweep from the debrief spec (update durable pages, bump
their verified-date, deprecate what the change replaced).Whatever ran inline gets named in the verdict ("debrief ran inline — no debrief skill installed"), so the close is honest about its own machinery.
Claude Code (plugin, recommended — full bundle: ship-pipeline reference, HTML report machinery, bundled session-debrief):
/plugin marketplace add DevOtts/conclude-it
/plugin install conclude-it@devotts
Any SKILL.md-compatible agent (Cursor, Codex CLI, Copilot, OpenCode, Windsurf, …):
npx skills add DevOtts/conclude-it -a <agent> # peek first: npx skills add DevOtts/conclude-it --list
gh skill install DevOtts/conclude-it # GitHub CLI alternative
Getting started: at the end of any working session —
/conclude-it
Plain sessions get the close core (debrief → ledger card → verification → reap →
sweep → verdict). Sessions that shipped get the full ship pipeline first — gates,
deploy, prod verification, archive — and a local CONCLUDE_REPORT.html you open
in the browser to double-check everything with "How to test" steps per item.
Authored by DevOtts.
[!NOTE] The lifecycle family — plan-it plans it, build-it builds it, review-it reviews it, conclude-it concludes it:
plan-itplans →build-itbuilds →review-itverifies → conclude-it concludes. This is the last stage: the work is built and reviewed; conclude-it ships it, proves it in prod, files the knowledge, cleans the debris, and closes the session. (prompt-itcompiles the prompts that start it all.)
Every long agent session ends the same way: you type the quit and hope. Hope the knowledge that existed only in the conversation got written down somewhere. Hope the feature you merged actually works in prod. Hope no background job is still running, no worktree is left dangling, no credential got echoed into a file on a remote host at 2am.
conclude-it replaces the hope with a ritual. One command, every close. A mechanical triage looks at what the session actually did — deploys run, feature work at the merge boundary, a Definition of Done met without prod verification — and picks the leg for you:
Then every session, both legs, gets the same close core: debrief the knowledge into durable docs, write the session-history ledger card, verify nothing is mid-flight, reap idle subagents, sweep the session's own footprint (secrets at rest first), and end with a verdict you can trust.
Because the failure modes of ending a session are quieter than the failure modes of running one — and they compound:
| Without a ritual | With conclude-it |
|---|---|
| "Done" means "the code is written" | Done means green in prod, or it's loudly labeled "deployed-but-unverified" |
| Session knowledge dies with the transcript | Debrief promotes it into durable docs — and a supersession sweep retires the docs the change replaced, so you never keep two "current" pages describing two versions of one feature |
| "Which session did X?" means re-reading transcripts | A ≤40-line ledger card per session answers it for ~150 tokens |
| Zombie subagents hold RAM; orphaned processes linger | Finished agents reaped; headless processes killed by exact recorded PID only |
| Worktrees, scratch files, and the occasional credential accumulate | The footprint sweep removes what the session can prove it created — secrets first, verified absent — and reports what it deliberately left |
| The summary shows the green half | The verdict and the HTML report show every state — RED and UNVERIFIED get their own badges |
The honest claim: conclude-it doesn't make your tests pass or your deploy work. It makes it impossible to close a session on top of a failure without seeing it named.
conclude-it ships as both a Claude Code plugin and a standard repo-root
SKILL.md, so it installs across the whole agent ecosystem. Pick your tool
below.
[!TIP] Two universal installers understand the
SKILL.mdstandard and drop conclude-it into the right directory for 70+ tools — use these if your agent isn't listed:npx skills add DevOtts/conclude-it -a <agent> # e.g. -a codex, -a cursor, -a github-copilot ; add -g for global gh skill install DevOtts/conclude-it # GitHub CLI (project or user scope)Peek first with
npx skills add DevOtts/conclude-it --list.
# 1. Register the marketplace
/plugin marketplace add DevOtts/conclude-it
# 2. Install the plugin (plugin-name@marketplace-name)
/plugin install conclude-it@devotts
The marketplace name devotts comes from the name field in
marketplace.json. This is the only target
that gets the full bundle — the conductor with its progressive-disclosure ship
pipeline, the deterministic build-report.py + HTML template machinery, and
the bundled generic session-debrief, with slash-command invocation and
auto-activation. (Skills-CLI alternative: npx skills add DevOtts/conclude-it -a claude-code.)
npx skills add DevOtts/conclude-it -a codex
# or: gh skill install DevOtts/conclude-it
Installs to the shared .agents/skills/conclude-it/ that Codex reads. Codex
doesn't carry the bundled machinery, so conclude-it runs the debrief inline
and writes the closeout report as markdown (graceful degradation) — you still
get the triage, the fail-closed gates, the ledger card, the sweeps, and the
honest verdict.
npx skills add DevOtts/conclude-it -a openclaw
Lands in .openclaw/skills/conclude-it/SKILL.md.
npx skills add DevOtts/conclude-it -a cursor # add -g for a global install
Installs into Cursor's .agents/skills/ and is auto-discovered.
npx skills add DevOtts/conclude-it -a github-copilot
# or: gh skill install DevOtts/conclude-it
Copilot auto-discovers skills under .agents/skills/.
gh skill install DevOtts/conclude-it
# or: npx skills add DevOtts/conclude-it -a github-copilot
gh skill install DevOtts/conclude-it
If your Kiro build doesn't yet read the shared skills path, drop the skill in manually:
git clone https://github.com/DevOtts/conclude-it /tmp/conclude-it
mkdir -p "<kiro-skills-dir>/conclude-it" && cp /tmp/conclude-it/SKILL.md "<kiro-skills-dir>/conclude-it/"
npx skills add DevOtts/conclude-it -a <agent>
Run npx skills add DevOtts/conclude-it --list, then target your agent — the
CLI knows the correct path for each. Manual fallback for any tool: clone the
repo and copy the root SKILL.md into your agent's
skills/instructions directory.
[!NOTE] On every target except Claude Code, conclude-it installs as a single self-contained skill (the root
SKILL.md— it carries the full flow, ship pipeline included). The HTML report machinery, the bundledsession-debrief, and delegated helpers like/iterateand/full-qaare Claude Code plugin pieces; elsewhere conclude-it runs those phases inline, writes the closeout report as markdown, and names the absence in its verdict instead of pretending. The thing that ports everywhere is the ritual — the gates, the sweeps, and the honesty.
/conclude-it # at the end of any session — the triage picks the leg
Also answers to plain language: "close this session", "wrap up and exit", "ship it and close", "I'm done for now", "is it safe to exit?".
The first time you close a session in a repo, conclude-it runs a five-question setup interview — and it detects before it asks, so most questions arrive pre-answered for you to confirm:
<project>-deploy
skill with this repo's exact deploy instructions, and offers to scaffold it
from what it already knows. Until then, deploys run inline via your
documented path.<project>-debrief skill describing how your
docs structure works; otherwise the bundled generic session-debrief.The answers are saved as a small block inside the repo (CLAUDE.md /