issue

Create structured GitHub issues with semantic titles and task checklists.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/smykla-skalski/harness --skill issue-smykla-skalski
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: issue
Source: https://github.com/smykla-skalski/harness/tree/main/.claude/skills/issue
Command: npx skills add https://github.com/smykla-skalski/harness --skill issue-smykla-skalski

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill turns vague reports, feature requests, and ad-hoc tasks into actionable, test-driven GitHub issues so work can be picked up and completed reliably without extra clarification.

Core Features & Use Cases

  • Guided fast mode that formats user input into a semantic title, concise description, labels, and a precise task checklist.
  • Deep investigation mode that reads the codebase to confirm bugs, identify root causes, and reference files or functions before drafting.
  • Integrated publishing helpers for image uploads, title validation, humanized prose, GitHub publishing, and post-creation render verification.
  • Use cases: filing bugs, proposing enhancements, documenting task scopes, or creating tracked work items for the smykla-skalski/harness repository.

Quick Start

Ask the skill to create an issue by saying /issue followed by a short description or add --deep to run a full investigation before drafting.

Frequently Asked Questions about issue

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

FAQPage Schema
How do I create GitHub issues that turn vague bug reports into actionable tasks?▼

To create actionable GitHub issues, use a guided fast formatting mode that applies semantic type(scope): description titles, concise descriptions, suggested labels, and TDD-aligned task checklists.

What is deep investigation mode for GitHub issue triage?▼

Deep investigation mode reads the codebase to confirm bugs, identify root causes, and reference specific files or functions before drafting a structured GitHub issue with validated titles and task checklists.

Can I use TDD-aligned task checklists when filing GitHub feature requests?▼

Yes, you can file feature requests and bugs using TDD-aligned task checklists that ensure work items are picked up and completed reliably without requiring extra clarification.

Does this GitHub issue automation support image uploads and post-creation rendering verification?▼

Yes, integrated publishing helpers support image uploads, title validation, humanized prose, GitHub publishing, and post-creation rendering verification for generated GitHub issues.

What is the best way to format GitHub issue titles for automated triage?▼

The best way to format issue titles for triage is using semantic type(scope): description naming, which validates titles and applies appropriate labels for bugs, enhancements, and documentation updates.