issue-folding

Classify bounded issue packets into actionable, duplicate, superseded, or no-op dispositions.

4|1|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/danielbaustin/agent-design-language --skill issue-folding
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-folding
Source: https://github.com/danielbaustin/agent-design-language/tree/main/adl/tools/skills/issue-folding
Command: npx skills add https://github.com/danielbaustin/agent-design-language --skill issue-folding

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill helps teams triage bounded issue packets by classifying dispositions (actionable, duplicate, superseded, absorbed into another issue, already_satisfied, obsolete, or blocked) and routing the appropriate handoff with evidence preserved.

Core Features & Use Cases

  • Issue disposition classification: analyzes issue packets or task bundles to determine whether work should proceed, be folded into an existing issue, or be closed with clear handoff guidance.
  • Evidence preservation: extracts and records cause markers and linked references (issues/PRs) to support audit trails.
  • Handoff guidance and safety: returns a structured contract with status, classification, closure_outcome, worktree_action, and recommended_handoff for downstream tooling.

Quick Start

Provide a bounded issue packet or task bundle to generate a folding report for review and routing.

Frequently Asked Questions about issue-folding

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

FAQPage Schema
How do I triage GitHub issues to determine if they should be closed or folded into another issue?

Issue folding classifies bounded issue packets by disposition, determining whether work is actionable, duplicate, superseded, or obsolete. It extracts linked PR references to generate a structured handoff contract with evidence preserved for audit trails.

What is the best way to preserve evidence when closing duplicate GitHub issues?

Evidence-backed folding records cause markers and linked issue references during classification to maintain audit trails. The structured contract includes status, classification, and closure outcome, ensuring downstream tooling receives clear handoff guidance with all routing evidence preserved.

How does issue classification handle blocked or already satisfied task bundles?

Issue folding evaluates bounded task bundles to classify dispositions including already_satisfied, blocked, or absorbed into another issue. It analyzes source prompts and linked surfaces to produce a recommended handoff, routing the work appropriately based on the extracted evidence.

Can I automate issue routing handoffs for downstream workflow tooling?

Yes, issue folding produces a structured contract containing status, worktree action, and recommended handoff specifically for downstream tooling. Providing a bounded issue packet or task bundle generates a folding report that routes dispositions with evidence-backed guidance.

When should I use issue folding for triaging task bundles instead of manual review?

Issue folding is suited for bounded issue packets or task bundles needing structured disposition classification and evidence preservation. It benefits teams requiring consistent routing guidance, cause marker extraction, and structured handoff contracts for audit trails over manual triage.

Does issue folding work without external dependencies to classify issue dispositions?

Yes, issue folding operates independently without external dependencies to classify issue dispositions. It processes the bounded issue packet internally, extracting source prompts and linked references to determine the appropriate routing and closure outcome.