Dev10x:session-wrap-up

Capture open tasks, uncommitted changes, and pull requests into session.yaml.

7|2|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/Dev10x-Guru/Dev10x-Claude --skill dev10x-session-wrap-up-dev10x-guru
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Dev10x:session-wrap-up
Source: https://github.com/Dev10x-Guru/Dev10x-Claude/tree/main/skills/session-wrap-up
Command: npx skills add https://github.com/Dev10x-Guru/Dev10x-Claude --skill dev10x-session-wrap-up-dev10x-guru

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires TaskList, git, mcp__plugin_Dev10x_cli__pr_detect, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps manage open work items at the end of a development session, ensuring nothing is lost and project continuity is maintained.

Core Features & Use Cases

  • Session End Automation: Automatically identifies and routes open work items when a session ends.
  • Task Tracking: Captures all in-progress tasks, uncommitted changes, and open pull requests.
  • User Interaction: Allows users to finish, defer, or drop open items directly within the session-wrap-up flow.
  • State Persistence: Saves session state for resumption in future sessions.
  • Use Case: After a development session, use this Skill to review open tasks, review code changes, and decide the next steps for each item.

Quick Start

Use the command '/Dev10x:session-wrap-up' to automatically capture and manage open work items at the end of your session.

Frequently Asked Questions about Dev10x:session-wrap-up

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

FAQPage Schema
How do I automate session wrap-up and track open tasks before ending a development session?

Session wrap-up automation captures in-progress tasks, uncommitted git changes, and open pull requests, allowing you to finish, defer, or drop items to maintain project continuity.

What is the best way to manage uncommitted git changes and open pull requests at the end of a coding session?

Managing uncommitted git changes and open pull requests at session end involves detecting open work items, routing them for review, and persisting the session state to a yaml file for future resumption.

How do I save and restore task tracking state across multiple development sessions?

Save and restore task tracking state by capturing open work items and persisting session details to the .claude/Dev10x/session.yaml file, ensuring deferred tasks are ready for future sessions.

Do I need TaskList and git to capture and defer open work items during session closure?

Yes, capturing and deferring open work items during session closure requires the TaskList plugin for task tracking, git for uncommitted change detection, and a PR detection tool for pull requests.

Can I use session wrap-up automation to review code changes and decide next steps for in-progress tasks?

Yes, session wrap-up automation allows you to review code changes and decide next steps for each in-progress task by presenting options to finish, defer, or drop open items directly within the flow.

What happens to deferred tasks when session state is persisted to a yaml file?

When session state is persisted to the session.yaml file, deferred tasks and open work items are captured and stored, allowing you to seamlessly resume project continuity in future development sessions.