git404hub

what is claude-close-skill fr?

artformoney/claude-close-skill — explained in plain English

Analysis updated 2026-05-18

0Audience · developerComplexity · 2/5Setup · easy

tl;dr

A /close skill for Claude Code that ends each session with a debrief and a short rolling handoff briefing for the next one.

vibe map

mindmap
  root((close skill))
    What it does
      Ends sessions with a handoff
      Debriefs before writing files
      Caps briefing at 60 lines
    Tech stack
      Claude Code
      Shell
      Markdown
    Use cases
      Keep a rolling handoff briefing
      Run project close duties
      Detect an unclosed session
    Audience
      Claude Code users
      Developers
    Features
      Debrief first sequence
      Append only session log
      SessionStart staleness warning

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

what do people make with this?

VIBE 1

Install the /close skill so every Claude Code session ends with a clean handoff briefing.

VIBE 2

Keep a rolling 60 line HANDOFF.md instead of letting session notes pile up unread.

VIBE 3

Add project specific close-duties.md checks so recurring wrap up tasks are not forgotten.

VIBE 4

Get warned at the start of a session when the previous one crashed without closing properly.

what's the stack?

Claude CodeShellMarkdown

how it stacks up fr

artformoney/claude-close-skill00kaku/gallery-slider-block04amanrajj/netwatch
Stars00
LanguageJavaScriptRust
Last pushed2021-05-19
MaintenanceDormant
Setup difficultyeasyeasymoderate
Complexity2/52/53/5
Audiencedevelopergeneralops devops

Figures from each repo's GitHub metadata at analysis time.

how do i run it?

Difficulty · easy time til it works · 5min

The staleness check hook uses macOS date syntax and needs a small edit on Linux.

Unknown from the shown README, check the repository license file for exact terms.

in plain english

claude-close-skill provides a slash command called /close for Claude Code that ends a working session cleanly by handing its important state to whatever session comes next. The idea is to work in short, fresh sessions rather than keeping one long running chat alive for weeks, since a chat that has been running that long ends up dragging around old dead ends and pasted error output, which makes answers feel worse even though the underlying model has not changed. It also addresses the surprise cost of coming back to an old conversation after a break, since a long idle chat loses its cheap cache and a tiny message like a simple greeting ends up reprocessing the whole history. The skill's answer is to treat a chat window less like a database. Before writing anything to disk, the close routine has the model debrief with you in the conversation itself, describing what it is least sure about and what might be lost once the context window closes, so your response can shape what actually gets recorded. It then rewrites a single briefing file capped at 60 non blank lines, describing the project as it stands right now rather than appending to a growing pile of dated notes, appends a short entry to a running session log, and files anything more durable into the project's own permanent documents. It can also run project specific closing duties defined in a separate file, each one gated on whether that duty's condition actually happened during the session, and it notices when a previous session ended without closing properly by checking the gap at the start of the next one. Installing it means copying one global skill file into your Claude configuration folder, then wiring a session start hook and a pointer in each project either by accepting the skill's own offer to set it up or by copying an example settings file. A macOS specific date command is used for the staleness check, which needs a small edit to work on Linux. The project has no stated license in the shown README.

prompts (copy fr)

prompt 1
Copy SKILL.md into ~/.claude/skills/close and wire the SessionStart hook for this project.
prompt 2
Explain why this close skill rewrites HANDOFF.md instead of appending dated blocks.
prompt 3
Walk me through writing a close-duties.md file with a gate and do shape for my project.
prompt 4
Help me port the staleness check's date command from macOS syntax to GNU/Linux syntax.

Frequently asked questions

what is claude-close-skill fr?

A /close skill for Claude Code that ends each session with a debrief and a short rolling handoff briefing for the next one.

What license does claude-close-skill use?

Unknown from the shown README, check the repository license file for exact terms.

How hard is claude-close-skill to set up?

Setup difficulty is rated easy, with roughly 5min to a first successful run.

Who is claude-close-skill for?

Mainly developer.

peek the repo → explain another one

This repo across BitVibe Labs

double-check against the repo, no cap.