check-handoffs

Scans inbox for HANDOFF-*.md files and reports sender, date, and summary.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/hilbertp/liberation-of-bajor --skill check-handoffs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check-handoffs
Source: https://github.com/hilbertp/liberation-of-bajor/tree/main/.claude/skills/check-handoffs
Command: npx skills add https://github.com/hilbertp/liberation-of-bajor --skill check-handoffs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps role-based contributors discover and surface incoming handoff files addressed to them so work items are not missed and pre-session bookkeeping is validated.

Core Features & Use Cases

  • Inbox scanning: Lists HANDOFF-*.md files in the repository inbox for the current role and summarizes file path, sender, date, and a one-line task summary.
  • T&T self-audit: Reads bridge/tt-audit.jsonl and bridge/timesheet.jsonl to detect gaps in time-and-task logging and displays a prominent warning when a timesheet entry is missing since the last audit.
  • Non-blocking token snapshot: Invokes the token snapshot script to capture a usage baseline without preventing the inbox check from proceeding.
  • Use case: When starting a new session or when asking "any handoffs for me?", run this skill to find waiting work, surface required preconditions, and confirm you should proceed.

Quick Start

Check my handoffs for the current role and list any HANDOFF files with sender, date, and a one-line summary.

Frequently Asked Questions about check-handoffs

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

FAQPage Schema
How do I find pending handoff files addressed to my role in a repository?

To find pending handoff files, scan the repository inbox at .claude/roles/{role-name}/inbox for HANDOFF-*.md files. The skill reports the file path, sender, date, and a one-line task summary for each waiting handoff item.

What is a pre-scan T&T self-audit for role-based workflow handoffs?

A pre-scan T&T self-audit validates time-and-task logging before checking an inbox by reading bridge/tt-audit.jsonl and bridge/timesheet.jsonl. It detects missing timesheet entries and displays a warning if a gap exists since the last audit.

How do I check my role inbox for HANDOFF files when starting a new session?

Check your role inbox by scanning the .claude/roles/{role-name}/inbox directory at session start. This surfaces waiting HANDOFF-*.md files with sender details and summaries, while a non-blocking token snapshot captures a usage baseline.

Can the inbox scan proceed if the token usage snapshot fails?

The inbox scan can proceed even if the token snapshot encounters issues because the script invocation is non-blocking. It captures a usage baseline via node bridge/usage-snapshot.js without preventing the handoff check from completing.

Does the handoff scanner work without external dependencies?

The handoff scanner works without external dependencies, relying only on internal repository files like bridge/tt-audit.jsonl, bridge/timesheet.jsonl, and node bridge/usage-snapshot.js to perform the inbox scan and T&T self-audit.

What limitations exist when scanning for missing timesheet entries?

A limitation when scanning for missing timesheet entries is that the audit only reads bridge/tt-audit.jsonl and bridge/timesheet.jsonl to detect gaps, displaying a warning rather than automatically creating or backfilling the missing time logs.