github-task-issue

Draft, validate, publish, and verify GitHub task issues with semantic titles.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill turns informal repo context, bug reports, UX findings, screenshots, or implementation notes into small, high-signal GitHub issues that are ready for an engineer to act on, eliminating ambiguous or oversized tickets and enforcing repository conventions.

Core Features & Use Cases

  • Scoped semantic titles: Enforces the repository semantic title format type(scope): description with a mandatory lowercase scope and validates the title before publication.
  • Drafting modes: Supports a fast mode that formats user input quickly and a deep mode that investigates code, reproductions, and evidence before drafting.
  • Humanize and approval gates: Requires explicit invocation of the humanize skill on saved drafts and an AskUserQuestion-style approval with exactly two outcomes before publishing.
  • Screenshot handling and render verification: Validates, uploads, and embeds screenshots correctly and verifies the rendered GitHub issue page for images, code formatting, and checklist items after creation.

Quick Start

Draft a scoped issue from the repository context, save the title and draft to a tmp/github-task-issue/<slug> workspace, invoke the installed humanize skill on the draft, validate the title, request explicit approval, publish using the included scripts, and verify the rendered issue page.

Frequently Asked Questions about github-task-issue

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

FAQPage Schema
How do I create well-structured GitHub issues from informal bug reports?

To create GitHub issues from informal bug reports, this Skill drafts and humanizes your input into small, semantically titled tickets. It formats context, screenshots, and implementation notes into high-signal issues ready for engineering action.

Does this issue drafting tool enforce semantic commit style titles?

Yes, this issue drafting tool enforces semantic titles using the type(scope): description format with a mandatory lowercase scope. It validates your title against repository conventions before publication to eliminate ambiguous tickets.

What's the best way to publish GitHub task issues with screenshot verification?

The best way to publish GitHub task issues with screenshot verification is to draft the content, upload and embed screenshots, then use validation and verification scripts. This process checks rendering for images, code formatting, and checklists after creation.

How does the humanize approval gate work before publishing a GitHub issue?

The humanize approval gate works by requiring the humanize skill to process your saved draft before requesting explicit user approval. You must approve exactly two outcomes before the publish script executes the GitHub issue creation.

Can I investigate code and reproduce bugs before drafting a GitHub issue?

Yes, you can investigate code and reproduce bugs before drafting a GitHub issue using the deep investigation mode. This mode examines code, reproductions, and evidence to draft high-signal tickets, while fast mode formats input quickly.

Why do my GitHub issues fail validation when publishing from drafts?

GitHub issues fail validation when publishing from drafts if the semantic title format type(scope): description is incorrect or the scope is not lowercase. The publish script gates on explicit approval and validates title structure before creation.