wrap-up

Evaluate repository compliance and append continuity notes to the decision log.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/stanz-stanz/heimdall --skill wrap-up-stanz-stanz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wrap-up
Source: https://github.com/stanz-stanz/heimdall/tree/main/.claude/skills/wrap-up
Command: npx skills add https://github.com/stanz-stanz/heimdall --skill wrap-up-stanz-stanz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a structured end-of-session evaluation that consolidates project state, flags compliance and hygiene issues, and prepares a continuity handoff so no work is lost between sessions.

Core Features & Use Cases

  • Live repository assessment: Runs git status, recent commits, diffs, and scans for TODO/FIXME markers to gather evidence for ratings.
  • Multidomain compliance review: Rates Valdí routing, agent boundaries, CLAUDE.md integrity, document consistency, and code hygiene as RED/AMBER/GREEN with concise reasoning.
  • Decision logging & checklist: Appends a dated decision entry to docs/decisions/log.md and produces an actionable checklist of items that need work, then requests confirmation before any edits.
  • Use Case: At the end of a development session, invoke this Skill to generate a prioritized handoff note, update the decision log, and produce a short prompt for the next session.

Quick Start

Ask the wrap-up skill to run a full end-of-session review and prepare the decision log.

Frequently Asked Questions about wrap-up

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

FAQPage Schema
How do I perform an end-of-session compliance check and generate a handoff note for my git project?

An end-of-session compliance check evaluates your repository's working tree, git status, and diffs to rate routing boundaries, document integrity, and code hygiene. It produces a decision log entry and an actionable checklist for continuity handoff.

What is a decision log entry for code project continuity and when do I need one?

A decision log entry consolidates project state and compliance issues into a dated record appended to docs/decisions/log.md. You need one during wrap-up, pre-commit, or end-of-day scenarios to ensure no work is lost between development sessions.

How do I scan for TODO and FIXME markers to assess code hygiene before committing?

Scanning for TODO/FIXME markers involves searching the repository working tree alongside git status and diff outputs. This evidence gathering rates code hygiene as RED, AMBER, or GREEN to flag issues requiring attention before session handoff.

Can I use a wrap-up review to check consistency across CLAUDE.md and SCANNING_RULES.md?

Yes, a wrap-up review checks CLAUDE.md and SCANNING_RULES.md consistency as part of its multidomain compliance evaluation. It verifies document integrity and agent SKILL.md boundaries, rating each domain with concise reasoning.

Does the end-of-day compliance review automatically edit the decision log?

No, the end-of-day compliance review requests confirmation before appending any dated decision entry to docs/decisions/log.md. It prepares the continuity notes and actionable checklist but waits for user permission to edit files.

What limitations exist when running a continuity evaluation on repositories without a docs/decisions/log.md file?

The continuity evaluation requires permission to append to docs/decisions/log.md for logging. Without this file path accessible in the repository, the decision logging and checklist generation cannot complete the handoff process.