bb-close-issue

Move handoff records to a closed archive and log the action.

41|9|Updated May 22, 2026
One-click install
npx skills add https://github.com/amoslee2026/Babel --skill bb-close-issue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bb-close-issue
Source: https://github.com/amoslee2026/Babel/tree/main/.claude/skills/bb-close-issue
Command: npx skills add https://github.com/amoslee2026/Babel --skill bb-close-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the closure of Babel design handoffs by safely moving the handoff record to a closed archive and logging the action, ensuring traceability and preventing stale handoffs.

Core Features & Use Cases

  • Move the handoff file from designs/<name>/.handoff/<label>.md to designs/<name>/.handoff/closed/ with a timestamped filename.
  • Append a standardized log entry to designs/<name>/.handoff/handoff_log.jsonl for auditability.
  • Optionally close the related GitHub issue via the gh CLI when --close-gh is true.
  • Validates inputs and executes a four-phase workflow: validate, move, append_log, and optional gh closure.

Quick Start

Run the command to close a handoff by specifying the design name and label, e.g., bb-close-issue --design-name mydesign --label handoff-123 --reason 'completed'.

Frequently Asked Questions about bb-close-issue

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

FAQPage Schema
How do I automatically close design handoff issues in a multi-agent workflow?

To automatically close design handoff issues, use a skill that moves handoff records to a closed archive, appends a timestamped log entry, and optionally closes the linked GitHub issue via the gh CLI when triggered with specific parameters.

What is the best way to archive design handoff files and maintain an audit log?

Archiving design handoff files safely requires moving the record to a closed directory with a timestamped filename and appending a standardized entry to a JSONL log file, which ensures full traceability and prevents stale handoffs from accumulating.

Can I close the related GitHub issue when marking a design handoff as completed?

Yes, you can close the related GitHub issue by enabling the --close-gh flag during the handoff closure process, which triggers the gh CLI to automatically close the issue after the handoff file is archived and logged.

How do I log design handoff closures for multi-agent traceability?

Logging design handoff closures involves appending a standardized entry to the handoff_log.jsonl file within the design's directory, creating an auditable trail that tracks when and why each handoff was moved to the closed archive.

What parameters do I need to run the bb-close-issue handoff closure command?

Running the bb-close-issue command requires specifying --design-name, --label, and --reason parameters to validate and process the handoff, with an optional --close-gh flag to trigger GitHub issue closure.

Does the design handoff closure workflow validate inputs before moving files?

Yes, the design handoff closure workflow executes a four-phase flow starting with validation, ensuring all required input parameters are correct before moving the handoff file, appending the log, and optionally closing the GitHub issue.