harnessloop-issuelisted

Use when the user references harnessloop:issue or asks to record, analyze, or propose a fix for a Harnessloop evolution issue, framework question, protocol defect, self-audit concern, skill gap, template gap, packaging gap, or plugin behavior problem. This skill records user questions as evolution issues and analyzes them without copying project-private context.
litianyi-007/harnessloop · ★ 0 · AI & Automation · score 67

Install: claude install-skill litianyi-007/harnessloop

# Harnessloop Issue Use this skill when the input is a user question about Harnessloop itself, a request to record a Harnessloop concern, an issue report from `.harnessloop/meta/evolution-issues/`, or an equivalent Harnessloop self-audit report. The goal is to improve Harnessloop itself. Do not solve the source project's business problem unless that is required to understand the Harnessloop failure. ## Input Contract Accept an explicit skill invocation such as: - `$harnessloop-issue record <question or concern>` - `$harnessloop-issue analyze .harnessloop/meta/evolution-issues/0001-example.md` - `$harnessloop-issue propose-fix .harnessloop/meta/evolution-issues/0001-example.md` Treat `harnessloop:issue` as a natural-language alias only; `$harnessloop:issue` is not a valid skill invocation. Supported actions: - `record`: create or draft an evolution issue from a user question, concern, self-audit finding, unclear protocol behavior, missing skill behavior, template gap, packaging gap, or plugin problem. - `analyze`: classify an existing issue and identify the smallest upstream improvement. - `propose-fix`: produce the smallest upstream patch outline or apply it when the user explicitly asks for code changes. For `record`, useful input includes: - Summary of the question or suspected Harnessloop problem. - Expected Harnessloop behavior. - Actual or observed behavior. - Scope: docs, template, main loop, issue skill, another skill, examples, validation script, plugin pack