skills.rest
code0100fun
code0100funCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

session-completion

Create follow-up issues, run tests and linters, and prepare handoff summaries.

1|1|Updated Feb 8, 2026
Search Tags:#git#workflow#handoff#session#issue-tracking#quality-gates
One-click install
npx skills add https://github.com/code0100fun/botfiles --skill session-completion
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: session-completion
Source: https://github.com/code0100fun/botfiles/tree/main/plugins/workflow-tools/skills/session-completion
Command: npx skills add https://github.com/code0100fun/botfiles --skill session-completion

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When ending a work session, complete these steps to ensure clean handoff and no lost context.

Core Features & Use Cases

  • Create issues for follow-up work, including bugs, partially implemented features, technical debt, or ideas.
  • Run quality gates (tests, linters/formatters, builds) to verify changes before closing the session.
  • Update issue statuses and document decisions to keep stakeholders aligned.
  • Commit changes with meaningful messages and prepare for handoff, without pushing automatically.

Quick Start

End the session by filing remaining issues, running quality gates, updating statuses, and handing off context for the next session.

Frequently Asked Questions about session-completion

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

FAQPage Schema
How do I automate clean session completion and handoff when wrapping up coding work?▼

Automate clean session completion by creating follow-up issues, running tests and linters, updating issue statuses, and preparing a handoff summary to ensure no lost context across repositories.

What steps are needed for a clean git workflow handoff at the end of a development session?▼

A clean git workflow handoff requires filing remaining issues, running quality gates, updating issue statuses, and committing changes with meaningful messages while avoiding automatic pushes.

Do I need issue tracker and test command access to enforce quality gates before closing a session?▼

Yes, session completion requires access to project tooling including an issue tracker, test commands, and git to enforce quality gates and integrate with standard workflows.

Can I commit changes during session completion without automatically pushing to the remote repository?▼

Yes, the session completion workflow enforces non-destructive commits and prepares a handoff summary without automatically pushing changes to the remote repository.

What types of follow-up issues should I create when ending a work session?▼

Create issues for follow-up work including bugs, partially implemented features, technical debt, or ideas to document decisions and keep stakeholders aligned for the next session.

Why run linters and formatters as quality gates before ending a development session?▼

Running linters, formatters, and builds as quality gates verifies changes before closing the session, ensuring the codebase remains stable and clean for the next developer.

Related Skills

Explore More Software Engineering Skills→
jwbaldwinjwbaldwin

work-on-ticket

Fetch Jira ticket details, create a kebab-case branch, and start task planning.

Community
Advanced
All-The-VibesAll-The-Vibes
50

land

Commit changes, push to the remote, and open a pull request for handoff.

Official
Advanced
joseph-c-mcguirejoseph-c-mcguire
1

06-tech-tooling

Set up and validate linters, formatters, and test runners for CI builds.

Community
Advanced
SentioLabsSentioLabs
1

finish

Run end-of-session workflows for Arc by capturing work, running quality gates, and committing changes.

Official
Advanced