kb-session-wrap-scan

Generate non-mutating W0/W1/W2 wrap-up scan reports for a session-id.

2|1|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/Remaker-Digital/groundtruth-kb --skill kb-session-wrap-scan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kb-session-wrap-scan
Source: https://github.com/Remaker-Digital/groundtruth-kb/tree/main/.claude/skills/kb-session-wrap-scan
Command: npx skills add https://github.com/Remaker-Digital/groundtruth-kb --skill kb-session-wrap-scan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill solves the problem of catching session wrap-up issues early by running a non-mutating scan that highlights hygiene problems and cross-artifact inconsistencies before any mutating wrap procedure is allowed to proceed.

Core Features & Use Cases

  • W0 transcript-manifest capture (non-mutating): Records session manifest context (git HEAD/branch plus uncommitted/untracked status) into the snapshot directory for later review.
  • W1 hygiene scan with severity: Produces a markdown hygiene report and communicates advisory vs error-severity via a strict exit-code contract (0 vs 2).
  • W2 cross-artifact consistency check: Generates a markdown consistency report to verify coherence across related artifacts, using the same error-severity exit-code contract.

Use case: Before running the mutating /kb-session-wrap for an AI development session, review the generated reports under .groundtruth/session/snapshots/<session-id>/ to decide whether to proceed or request fixes.

Quick Start

Run /wrap-scan S310 to generate the W0, W1, and W2 slice-1 wrap-up scan reports into the session snapshot directory for owner review.

Frequently Asked Questions about kb-session-wrap-scan

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

FAQPage Schema
How do I run a non-mutating preflight check before finalizing an AI session wrap-up?

Run a non-mutating preflight check by executing the wrap-up scan scripts for a specific session-id, generating W0, W1, and W2 markdown reports into the session snapshot directory without altering the KB state.

What is a hygiene scan and how does it validate session artifacts?

A hygiene scan validates session artifacts by producing a markdown report that highlights hygiene problems and cross-artifact inconsistencies, communicating advisory versus error severity through a strict exit-code contract.

Can I use this consistency check in CI pipelines without modifying my knowledge base state?

Yes, the consistency check enforces read-only behavior suitable for CI preflight pipelines, writing only to the session snapshots directory and returning exit code 2 whenever error-severity results are encountered.

What is the exit code contract for the W1 and W2 markdown reports?

The W1 and W2 markdown reports use a strict exit-code contract where advisory-severity results return exit code 0 and any error-severity results return exit code 2 to halt mutating workflows.

How do I capture git context during a session wrap-up review?

Capture git context during a wrap-up review using the W0 transcript-manifest capture, which records the git HEAD, branch, and uncommitted or untracked file status into the snapshot directory for later owner review.

When should I avoid running a mutating knowledge base session wrap?

Avoid running a mutating wrap when the non-mutating scan reports reveal error-severity hygiene or consistency issues, requiring fixes before proceeding with the mutating wrap-up procedure.