Rectify: collapse-issues Content Fidelity — Issue Body Data Lineage

[Trecek]

Summary

collapse-issues assembled multi-issue combined bodies by fetching all bodies in bulk via gh issue list --json body — which truncates content at ~256 characters — and then instructing the LLM to insert <full body of issue N, verbatim> into the output. The angle-bracket syntax signaled a fill-in-the-blank template slot, causing the LLM to substitute a one-sentence summary or hyperlink rather than the actual body text. No contract test caught either defect.

The fix establishes a content-fidelity lineage contract: collapse-issues now calls fetch_github_issue per-issue (REST endpoint, full body) and uses explicit verbatim-paste language with a COPY MODE instruction. Three new contract tests enforce this for collapse-issues specifically, and a new cross-skill sweep (test_issue_content_fidelity.py) makes the defect structurally impossible in any future skill that assembles ## From #N body sections.

Requirements

FETCH — Source Issue Content Retrieval

• REQ-FETCH-001: The skill must fetch the full body of each source issue via gh issue view N --json body before composing the collapsed issue.
• REQ-FETCH-002: The skill must not summarize, truncate, or paraphrase source issue content during collapse.

INLINE — Content Inlining

• REQ-INLINE-001: The collapsed issue body must contain the complete body text from every source issue, inlined under clearly labeled sections.
• REQ-INLINE-002: Structured sections from source issues (requirements, acceptance criteria, design proposals, etc.) must be preserved verbatim in the collapsed output.
• REQ-INLINE-003: Each inlined section must identify its source issue number for provenance (e.g., "From feat: allow users to block or allow specific bundled skills and recipes #29").

SELF — Self-Containment

• REQ-SELF-001: A reader of the collapsed issue must be able to understand all source content without clicking through to original issues.
• REQ-SELF-002: Cross-reference links to originals must serve as provenance markers, not as substitutes for inlined content.

STALE — Staleness Handling

• REQ-STALE-001: When a source issue is known to be outdated, the collapsed issue must include a staleness note adjacent to that source's inlined content.

Architecture Impact

Data Lineage Diagram

%%{init: {'flowchart': {'nodeSpacing': 50, 'rankSpacing': 70, 'curve': 'basis'}}}%%
flowchart LR
    classDef cli fill:#1a237e,stroke:#7986cb,stroke-width:2px,color:#fff;
    classDef stateNode fill:#004d40,stroke:#4db6ac,stroke-width:2px,color:#fff;
    classDef handler fill:#e65100,stroke:#ffb74d,stroke-width:2px,color:#fff;
    classDef phase fill:#6a1b9a,stroke:#ba68c8,stroke-width:2px,color:#fff;
    classDef newComponent fill:#2e7d32,stroke:#81c784,stroke-width:2px,color:#fff;
    classDef output fill:#00695c,stroke:#4db6ac,stroke-width:2px,color:#fff;
    classDef detector fill:#b71c1c,stroke:#ef5350,stroke-width:2px,color:#fff;

    subgraph GitHub ["GitHub API"]
        BULK["● gh issue list<br/>━━━━━━━━━━<br/>number, title, labels<br/>body removed from query"]
        REST["fetch_github_issue<br/>━━━━━━━━━━<br/>GET /issues/{N} (REST)<br/>Full untruncated body"]
    end

    subgraph Skill ["● collapse-issues SKILL.md"]
        STEP3["● Step 3: Metadata Fetch<br/>━━━━━━━━━━<br/>number, title, labels only<br/>no body — grouping input"]
        STEP4["Step 4: LLM Grouping<br/>━━━━━━━━━━<br/>title + labels scoring<br/>form candidate groups"]
        STEP5["★ Step 5: Per-Issue Fetch<br/>━━━━━━━━━━<br/>fetch_github_issue per issue<br/>include_comments=true"]
        FETCHED["★ fetched_content[N]<br/>━━━━━━━━━━<br/>content.body field<br/>full untruncated text"]
        STEP6B["● Step 6b: Body Assembly<br/>━━━━━━━━━━<br/>SWITCH TO COPY MODE<br/>verbatim paste only"]
        NEVER["● NEVER Block<br/>━━━━━━━━━━<br/>no summarize/paraphrase<br/>no angle-bracket syntax<br/>no bulk body field"]
    end

    subgraph Output ["Combined Issue"]
        COMBINED["Combined Issue Body<br/>━━━━━━━━━━<br/>## From #N sections<br/>full verbatim content"]
    end

    subgraph Tests ["★ Contract Enforcement"]
        T1["● test_collapse_issues_contracts.py<br/>━━━━━━━━━━<br/>+ uses_per_issue_fetch<br/>+ never_summarize<br/>+ no_angle_bracket_placeholder"]
        T2["★ test_issue_content_fidelity.py<br/>━━━━━━━━━━<br/>cross-skill sweep:<br/>## From # → fetch_github_issue<br/>no angle-bracket syntax<br/>NEVER summarize block"]
        T3["● test_github_ops.py<br/>━━━━━━━━━━<br/>stale pytest.skip guards<br/>removed — tests active"]
    end

    BULK -->|"number,title,labels"| STEP3
    STEP3 -->|"issue list (no body)"| STEP4
    STEP4 -->|"qualifying groups"| STEP5
    STEP5 -->|"per-issue REST call"| REST
    REST -->|"full body"| FETCHED
    FETCHED -->|"content field"| STEP6B
    NEVER -.->|"constrains"| STEP6B
    STEP6B -->|"verbatim sections"| COMBINED

    T1 -.->|"enforces"| STEP5
    T1 -.->|"enforces"| NEVER
    T2 -.->|"cross-skill guard"| STEP5
    T3 -.->|"activates skipped tests"| T1

    class BULK handler;
    class REST stateNode;
    class STEP3 handler;
    class STEP4 phase;
    class STEP5 newComponent;
    class FETCHED newComponent;
    class STEP6B newComponent;
    class NEVER newComponent;
    class COMBINED output;
    class T1 detector;
    class T2 newComponent;
    class T3 detector;

Loading

Color Legend:

Color	Category	Description
Dark Blue	Input	Data origins and entry points
Orange	Handler	Existing fetch/processing steps
Purple	Phase	LLM control and grouping analysis
Green	New/Modified	★ New or ● modified components
Teal	Data	REST source (authoritative data)
Dark Teal	Output	Combined issue result
Red	Contract Tests	Enforcement guards

Closes #372

Implementation Plan

Plan file: /home/talon/projects/autoskillit-runs/remediation-372-20260314-205033-708941/temp/rectify/rectify_collapse-issues-content-fidelity_2026-03-14_205033.md

Token Usage Summary

Token Summary\n\nNo token data captured for this run.

🤖 Generated with Claude Code via AutoSkillit

[Trecek]

AutoSkillit PR Review — Verdict: changes_requested

[Trecek]

[warning] cohesion: test_collapse_issues_uses_per_issue_fetch, test_collapse_issues_never_summarize, and test_collapse_issues_no_angle_bracket_body_placeholder duplicate contract coverage already provided cross-skill by test_issue_content_fidelity.py. The same contracts are now enforced in two places for collapse-issues. Consider whether this skill-specific duplication is intentional (defense-in-depth) or should be removed.

[Trecek]

AutoSkillit review found 2 findings (1 actionable, 1 requiring human decision). See inline comments.

Actionable (changes_requested):

• L154: Local re import inside test body — move to module level for consistency

Needs decision:

• L119: Skill-specific tests (test_collapse_issues_uses_per_issue_fetch, test_collapse_issues_never_summarize, test_collapse_issues_no_angle_bracket_body_placeholder) duplicate cross-skill coverage in test_issue_content_fidelity.py — intentional defense-in-depth or removable redundancy?