One-click install
npx skills add https://github.com/derrybirkett/shulkerbox --skill wrap-up-derrybirkett
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wrap-up
Source: https://github.com/derrybirkett/shulkerbox/tree/main/skills/core/wrap-up
Command: npx skills add https://github.com/derrybirkett/shulkerbox --skill wrap-up-derrybirkett

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of reliably finishing a development session by staging changes, running safety checks, creating a conventional commit, bumping and pushing version tags, and preparing handover notes.

Core Features & Use Cases

  • End-of-session Git release workflow: checks status, stages changes, verifies common issues, drafts a conventional commit message, commits, tags the next version, and pushes to origin with tags.
  • Guardrails before committing: detects TODO/FIXME markers, warns on potentially sensitive files, highlights potential migration/refactor issues when docs aren’t updated, and validates directory-structure completeness.
  • Session continuity support: records the session summary in an activity log and optionally prepends actionable next steps to an inbox for the next session.

Quick Start

Run the wrap-up workflow by telling your AI to execute /wrap-up to commit staged changes, create and push a version tag, and generate handover notes.

Frequently Asked Questions about wrap-up

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

FAQPage Schema
How do I automate git commit, version tagging, and session handover at the end of a dev session?▼

To automate git commit and session handover, stage changes, run pre-commit safety checks, draft a conventional commit message, bump the version tag, push to origin main with tags, and record actionable handover notes.

What pre-commit checks should I run to prevent sensitive files from reaching origin main?▼

Pre-commit checks for sensitive files involve inspecting git status and diffs, scanning staged files for TODO/FIXME markers, flagging sensitive data, and warning about missing docs during migrations before pushing to origin main.

Does this workflow automation generate conventional commits automatically?▼

Yes, workflow automation drafts conventional commit messages based on staged changes and verifies directory-structure completeness before committing, bumping version tags, and pushing to origin main.

How do I maintain operational continuity between development sessions using git?▼

Maintaining operational continuity between development sessions requires recording a session summary in an activity log and optionally prepending actionable next steps to an inbox for the next working session.

Can I get warnings for migration issues before pushing version tags to origin?▼

Yes, you can receive warnings for potential migration or refactor issues when documentation isn't updated, alongside directory-structure validation, before committing and pushing version tags to origin main.

What is the best way to bump version tags and push them with git?▼

The best way to bump version tags and push them is to automate the end-of-session git workflow: stage changes, verify issues, create a conventional commit, tag the next version, and push to origin main with tags.