session-end

Scan for tech debt and summarize coding session outcomes.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/jforksy/claude-skills --skill session-end-jforksy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-end
Source: https://github.com/jforksy/claude-skills/tree/main/session-end
Command: npx skills add https://github.com/jforksy/claude-skills --skill session-end-jforksy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you close a coding session efficiently by identifying technical debt, summarizing progress, and capturing learnings to reduce post-session churn.

Core Features & Use Cases

  • Tech Debt Scan: Detect duplicated code, TODO/FIXME comments, incomplete implementations, missing tests, and shortcuts taken.
  • Session Summary: Provide a structured recap including Completed, In Progress, Blocked, and Next Steps.
  • CLAUDE.md Review: Encourage corrections or mistakes to be reflected as rules and propose self-improvement updates.
  • Commit Check: Ensure there are no uncommitted changes and flag files that should not be committed.

Quick Start

Run the session-end workflow to generate a wrap-up report for the latest coding session.

Frequently Asked Questions about session-end

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

FAQPage Schema
How do I scan for tech debt before ending a coding session?

To scan for tech debt before ending a coding session, you can run a wrap-up workflow that detects duplicated code, TODO/FIXME comments, incomplete implementations, missing tests, and shortcuts taken.

What is the best way to summarize coding session progress and next steps?

Summarizing coding session progress is best handled by a structured recap that categorizes outcomes into Completed, In Progress, Blocked, and Next Steps to reduce post-session churn.

How do I check for uncommitted changes before wrapping up a coding session?

To check for uncommitted changes during a coding session wrap-up, you can run a commit check that ensures there are no pending changes and flags files that should not be committed.

Can I update CLAUDE.md rules automatically at the end of a coding workflow?

You can update CLAUDE.md at the end of a coding workflow by prompting a review that encourages corrections or mistakes to be reflected as rules and proposes self-improvement updates.

Does the session-end workflow work for team development environments?

The session-end workflow is applicable to end-of-session wrap-ups for both individual developers and teams seeking structured closes, learnings, and next steps.

When do I need a structured coding session wrap-up?

You need a structured coding session wrap-up when you want to efficiently identify technical debt, capture learnings, and summarize progress to reduce post-session churn.