smith-finish

Automate end-of-session Git workflows by committing, pushing, and merging to main.

50|8|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/ATTCKDigital/smith --skill smith-finish
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: smith-finish
Source: https://github.com/ATTCKDigital/smith/tree/main/skills/smith-finish
Command: npx skills add https://github.com/ATTCKDigital/smith --skill smith-finish

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End-of-session workflow that ensures all work is committed, pushed, merged to main, specs are updated, and the workspace is clean. Prevents losing work when closing a development session.

Core Features & Use Cases

  • Automates end-of-session git operations: commit, push, and merge to main with PR creation or update.
  • Updates system specs and documentation to reflect the latest changes, ensuring traceability.
  • Cleans up the workspace by removing temporary artifacts and resetting the environment for the next session.
  • Use Case: When closing a coding session, smith-finish ensures all changes are captured in version control, merged appropriately, and the project state remains consistent for teammates.

Quick Start

Begin the smith-finish workflow to finish the current session and propagate changes to the main branch.

Frequently Asked Questions about smith-finish

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

FAQPage Schema
How do I automate end-of-session Git cleanup and pull requests?

Automating end-of-session Git cleanup and pull requests involves committing changes, pushing branches, merging to main, updating specifications, and cleaning the workspace. This workflow ensures all session work is captured in version control with traceable handoffs.

What is the best way to ensure my local branch changes are committed and merged before closing a coding session?

The best way to ensure local branch changes are committed and merged before closing a coding session is to use an automated workflow that commits, pushes, and creates or updates a pull request to main. This prevents data loss and maintains project consistency for teammates.

Does automated Git workflow cleanup guard against data loss when merging to main?

Yes, automated Git workflow cleanup guards against data loss when merging to main by enforcing safe Git practices. It only prompts for user input when decisions are genuinely ambiguous, ensuring no work is lost during the end-of-session handoff.

Can I update system specs and documentation automatically when finishing a Git workflow?

Yes, you can update system specs and documentation automatically when finishing a Git workflow. The automation updates project specifications to reflect the latest changes, ensuring traceability and a clean workspace for the next development session.

How to clean up temporary workspace artifacts after pushing a Git branch?

To clean up temporary workspace artifacts after pushing a Git branch, an automated end-of-session workflow removes temporary files and resets the environment. This ensures the project state remains consistent and ready for the next session.