Skip to content

Create-issue skill: Haiku delegation, 68% leaner instructions, eval suite #12

@oto-macenauer-absa

Description

@oto-macenauer-absa

Problem

The create-issue skill (added in b37262d) has several areas for improvement:

  1. Token cost — 347 lines of skill instructions loaded into context on every invocation; template discovery runs on the expensive primary model
  2. Narrow triggers — only activates on "create an issue", misses natural variations like "log a bug" or "submit a ticket"
  3. Shell fragility — uses --body-file - with stdin heredocs that break on PowerShell and special characters in markdown
  4. No test coverage — no eval suite to measure quality or catch regressions

Acceptance criteria

  • Template discovery delegated to Haiku subagent (cheaper model)
  • Instruction footprint reduced (target: <120 lines total across all files)
  • Trigger description covers common synonyms (bug report, ticket, problem, etc.)
  • Issue body posting works across PowerShell and Bash without quoting failures
  • Eval suite with at least 3 scenarios (bug, deep context, cross-repo)
  • Measured pass rate >= 95%

Metadata

Metadata

Labels

enhancementNew feature or request

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions