session-close

Automates end-of-session git workflow with push, rebase, and handoff steps.

Updated Nov 30, 2018
One-click install
npx skills add https://github.com/guygrigsby/dotfiles --skill session-close-guygrigsby
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-close
Source: https://github.com/guygrigsby/dotfiles/tree/main/opencode/skills/session-close
Command: npx skills add https://github.com/guygrigsby/dotfiles --skill session-close-guygrigsby

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Protocol for ending a coding session to ensure all work is committed, pushed, and handed off correctly.

Core Features & Use Cases

  • Enforces a complete end-of-session workflow with mandatory push to remote.
  • Guides issue creation, status updates, and handoff context for the next session.
  • Provides safe git operations and rebase recommendations to maintain clean history.

Quick Start

End your current coding session by following the steps to push all changes, close tasks, and hand off context to the next developer.

Frequently Asked Questions about session-close

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

FAQPage Schema
How do I automate end-of-session git workflow for code commits and handoff?

Automating end-of-session git workflow involves running a protocol that commits local changes, pushes to the remote repository, and generates handoff context. This ensures all session work is safely transferred and documented before ending.

What is the best way to ensure my coding changes are pushed before ending a session?

The best way to ensure changes are pushed is to enforce a mandatory push protocol as part of your end-of-session routine. This guarantees all local commits are synchronized with the remote repository and prevents lost work.

How do I safely rebase and push code when handing off to another developer?

To safely rebase and push code when handing off, follow a workflow that applies safe git operations and rebase recommendations to maintain a clean project history. This process checks for rebase safety before pushing the updated commit history to the remote.

Does this end-of-session workflow include issue tracking and PR awareness checks?

Yes, the end-of-session workflow includes issue tracking updates and PR awareness checks. It guides issue creation and status updates to ensure task context is properly handed off to the next development session.

What steps are needed to hand off coding context to the next session?

Handing off coding context requires pushing all changes to the remote, updating issue statuses, and documenting the current state for the next session. This ensures the next developer has all necessary context to continue the work.