session-close

Audits session changes against quality gates before ending a coding session.

1|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/arndvs/ctrlshft --skill session-close-arndvs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: session-close
Source: https://github.com/arndvs/ctrlshft/tree/main/skills/session-close
Command: npx skills add https://github.com/arndvs/ctrlshft --skill session-close-arndvs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Ending a coding session without verification leaves uncommitted changes, unstaged secrets, failing tests, and untracked follow-up work that silently degrades the codebase. This Skill runs a structured pre-flight audit so nothing in-scope is lost or left broken when the session closes. ## Core Features & Use Cases - Session Manifest Scoping: Derives exactly what this session produced (PRs, commits, issues, edited files) so out-of-scope work never blocks closing. - Five Quality Gates: Checks that changes are committed, no secrets are staged, a PR exists for the branch, and type checks, tests, and lint pass. - Two-Tier Open Items Report: Separates in-session blockers (Section A) from adjacent context (Section B) and produces an authoritative ready/not-ready verdict. - Use Case: Before wrapping up a feature branch, run the audit to confirm all commits are pushed, the PR is open, tests pass, and deferred items are filed as tracker tickets. ## Quick Start Ask the agent to run the session close checklist and audit this session before ending it.

Frequently Asked Questions about session-close

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify everything is committed before ending a coding session?▼

Run a session close audit that checks git status for uncommitted changes, lists unpushed commits, and confirms a PR exists for the current branch. It reports each gate as pass, fail, or skip with evidence.

How to check for secrets in staged git changes?▼

Scan staged filenames and diff content for patterns like .env, SECRET, API_KEY, TOKEN, and PRIVATE_KEY using grep on git diff output. This is a shallow heuristic that catches obvious key names but may miss vendor-prefixed or format-based tokens.

Does the session audit work without the GitHub CLI?▼

Yes, the PR existence check skips gracefully when the gh CLI is not installed or when the current branch is a base branch like main. Other gates such as tests, lint, and secrets scanning still run normally.

What happens to unfinished work when closing a session?▼

In-session items must be marked done, deferred to a tracker ticket, tackled immediately, or flagged as blocked by the user. Deferred items are not re-listed on re-runs, and only unresolved in-session items block the close verdict.

Why does the audit separate Section A from Section B items?▼

Section A contains work this session originated and owns, which drives the final verdict. Section B holds adjacent context like other sessions' commits or pre-existing tickets, which is informational only and never blocks closing.