wrapup

Automates end-of-session wrap-up including CLAUDE.md updates, build verification, and git push.

1|Updated Jan 23, 2026

Search Tags:#automation #git #workflow #build #claude #wrapup

Ready to run

npx skills add https://github.com/bobby-andris/Allied-FeedOps --skill wrapup-bobby-andris

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: wrapup
Source: https://github.com/bobby-andris/Allied-FeedOps/tree/main/.claude/skills/wrapup
Command: npx skills add https://github.com/bobby-andris/Allied-FeedOps --skill wrapup-bobby-andris

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End-of-session activity requires multiple manual steps and risk of drift; this skill automates the wrap-up sequence to ensure consistency and repeatability.

Core Features & Use Cases

Automates CLAUDE.md updates, build checks, and commit/push of session results.
Generates a continuation prompt when work remains unfinished, ensuring handoff clarity.
Provides a repeatable, auditable workflow suitable for team scrums and post-session summaries.

Quick Start

Run the /wrapup command to execute the complete wrap-up workflow and push changes automatically.

Frequently Asked Questions about wrapup

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

FAQPage Schema

How do I automate end-of-session git commit and push workflows?▼

Automating end-of-session workflows requires a tool that applies a standardized wrap-up sequence to update project context, verify builds, and commit results. This skill executes that sequence automatically via a single command.

What is a continuation prompt and when do I need one for my development workflow?▼

A continuation prompt provides handoff clarity when work remains unfinished. It is needed in development workflows when ending a session before tasks are complete, ensuring the next session can resume work accurately.

Can I automatically update CLAUDE.md files as part of my git workflow?▼

Yes, CLAUDE.md files can be updated automatically as part of a git workflow. The automation applies a standardized sequence that updates project context, runs build verification, and commits changes together.

Does the wrapup workflow require any dependencies or external components?▼

No dependencies or external components are required. The workflow operates independently to update CLAUDE.md, verify builds, generate continuation prompts, and handle git commit and push operations.

What's the best way to ensure consistency across end-of-session git operations?▼

The best way to ensure consistency is automating the wrap-up sequence rather than performing manual steps. Standardized automation eliminates drift risk and provides a repeatable, auditable workflow for post-session summaries.

Why does manual end-of-session workflow create drift risk?▼

Manual end-of-session workflows create drift risk because they require multiple manual steps that can be skipped or performed inconsistently. Automating the sequence ensures repeatability and eliminates human error.