Report Issue

Community

hegemonart

report-issue

Consent-gated GitHub issue reporter for /gdd. Triages locally against `reference/known-failure-modes.md`, layers Phase 22 secret-redaction with Phase 30 pseudonymization, drafts the payload to `.design/issue-drafts/`, opens `$EDITOR` for inspection, and submits via the user's `gh` CLI to a hardcoded repo only after explicit per-issue consent. Use when the user runs `{{command_prefix}}report-issue`, hits a failure on a whitelisted command with the `--report` flag, or asks to file a bug against get-design-done.

Overview

Publisher	hegemonart
Repository	`get-design-done`
Skill name	`report-issue`
Stars	3
Forks	1
Bundled files	1
License	MIT
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
1 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by hegemonart on GitHub. Read the source before you install it.

Installation

Install the Report Issue AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/hegemonart/get-design-done/tree/main/scripts/skill-templates/report-issue
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/hegemonart/get-design-done/tree/main/scripts/skill-templates/report-issue

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/hegemonart/get-design-done.git /tmp/get-design-done
mkdir -p .claude/skills
cp -r /tmp/get-design-done/scripts/skill-templates/report-issue .claude/skills/report-issue

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Report Issue in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Report Issue on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Report Issue is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

{{command_prefix}}report-issue

Local-first, consent-gated GitHub issue reporter. No auto-mode. Destination repo is hardcoded. The full step-by-step lives in report-issue-procedure.md; this file is the entry contract.

Pre-flight

If invoked without an error context (the user just typed {{command_prefix}}report-issue cold), ask in one round-trip: "What command failed and what was the error?" Capture command name + a paraphrase of the error. Don't interrogate - one short answer is enough to feed the triage matcher.

Steps

Kill-switch (D-08). Call isDisabled() from scripts/lib/issue-reporter/kill-switch.cjs FIRST. Either env (GDD_DISABLE_ISSUE_REPORTER=1) OR config (.design/config.json with { "issue_reporter": false }) makes the command unavailable. Surface the disable line via getDisableReason() ('env' wins when both set) and stop. No draft, no triage, no payload. {{command_prefix}}health mirrors the same line for at-a-glance verification.
Triage. Call matchKnownFailure(errorContext) from scripts/lib/issue-reporter/triage-matcher.cjs (Plan 30-03). If matched === true and --force-report is NOT set: print the suggested diagnosis + remedy, stop. Do NOT write a draft. (D-07)
Assemble. Call assemble(commandName, errorContext, trajectoryRef?, capabilityGapEvent?) from scripts/lib/issue-reporter/payload-assembly.cjs (Plan 30-02). This layers Phase 22 redact → Phase 30 pseudonymize, computes the fingerprint, and renders bilingual disclaimer + sections.
Draft. Call writeDraft({title, body, fingerprint}) from scripts/lib/issue-reporter/draft-writer.cjs. Print the absolute path: Draft written to .design/issue-drafts/<timestamp>-<fp8>.md. The file persists across decline - the user keeps their work either way. (D-04)
Dedup (D-06). Call searchByFingerprint(fingerprint, {destination}) from scripts/lib/issue-reporter/dedup.cjs. If degraded === true show a one-line warning and fall through to Step 5. If matches.length === 0 fall through to Step 5 unchanged. If matches.length >= 1 render the dedup UI listing each {number,title,url} with three actions per match: +1 → react(n, {destination}) (no new issue, D-06), me-too → commentMeToo(n, {destination, errorContext, runtime, pluginVersion}) body is EXACTLY 3 fields (last error line, runtime, plugin version) from the ALREADY-pseudonymized 30-02 pipeline (D-01), new → fall through to Step 5 with the prepared draft despite the match.
Edit. If $EDITOR is set, the consent prompt opens it on the draft and blocks until exit. Otherwise the path is printed and the user can open it manually. EDITOR is the only env var the report flow reads.
Consent. Call promptConsent({draftPath}) from scripts/lib/issue-reporter/consent-prompt.cjs. Re-reads the (possibly edited) draft from disk, prints a summary, asks Submit this issue to hegemonart/get-design-done? [y/N]. Anything other than y/yes declines. (D-03)
- Throws if process.stdin.isTTY is false (no auto-mode).
- Throws if any process.env key matching /REPORT|ISSUE|AUTO_REPORT/i is set to a truthy value.
Submit. On y, call submitViaGh({title, body}) from scripts/lib/issue-reporter/gh-submit.cjs. This spawns gh issue create --repo hegemonart/get-design-done --title <title> --body-file <tmp>. Destination is hardcoded; no env var or flag can redirect it. (D-02 + D-05)
gh-absent fallback (D-10). If detectGh() from scripts/lib/issue-reporter/gh-absent-fallback.cjs returns false BEFORE Step 7 runs: call runFallback(consent.finalBody) to copy the (already-pseudonymized) payload to the clipboard via the platform's clipboard command (pbcopy on macOS, wl-copy/xclip on Linux, clip.exe on Windows) and print the message gh CLI not found; payload copied to clipboard, paste into the link below. followed by the issue-template URL. The draft persists on disk for re-submission once gh is installed.

Use through `--report`

Whitelisted to specific commands via scripts/lib/issue-reporter/cli-flag-report.cjs. Only gdd:plan-phase, gdd:execute-phase, and gdd:report-issue itself install the flag - and only when reference/known-failure-modes.md has at least one propose_report: true entry. Non-whitelisted commands silently do not see the flag. (D-11)

Use through `--force-report`

Available on {{command_prefix}}report-issue. Overrides the triage gate (Step 1) but does NOT override consent. The user still gets the draft + consent prompt. There is no path to submit without an explicit y.

Privacy contract

Pseudonymization, not anonymization. Disclaimer (Russian + English) is rendered at the top of the payload by Plan 30-02. Side-channel content (writing style, code patterns) may still re-identify. The user reviews the exact bytes before consenting.
No auto-mode, no env-var bypass. Static tests (tests/report-issue-no-auto-submit-static.test.cjs) fail the build if anyone adds a process.env.*REPORT*/*ISSUE*/*AUTO_REPORT* read here or under scripts/lib/issue-reporter/. Runtime check in consent-prompt.cjs is the second layer.
Hardcoded destination. scripts/lib/issue-reporter/destination.cjs is the only file that contains the literal repo string; it exports a frozen object so runtime tampering throws. Static tests enforce both invariants.
No HTTPS, no fetch. Submission goes through the user's gh CLI only. Plan 30-07 ships a CI gate that fails the build if any network primitive is added here.

Troubleshooting

gh not authenticated. The submission step fails with a clear error pointing to the draft path. Run gh auth login and re-invoke {{command_prefix}}report-issue - the draft survives.
No EDITOR set. The path is printed; open it in whatever editor you prefer, save, then return to the consent prompt.
Triage matched something irrelevant. Pass --force-report to bypass the gate. Consent is still required.
gh not installed (D-10). After consent, the payload is copied to your clipboard and an issue-template URL is printed. Paste into the URL to file manually. Install gh later and the existing draft can be re-submitted.
Command unavailable / disabled (D-08). Run {{command_prefix}}health. The issue reporter: line shows the active disable surface - either disabled by env (GDD_DISABLE_ISSUE_REPORTER=1) or disabled by config (.design/config.json: issue_reporter=false). Unset the env var or flip the config key to re-enable.

See report-issue-procedure.md for the full procedure with rationale per decision (D-02, D-03, D-04, D-05, D-07, D-11).

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

report-issue-procedure.md11 KB

Frequently asked questions

What does the Report Issue AI skill do?

Why use Report Issue on TypingMind?

Because you install it once and use it with any model. Report Issue is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Report Issue in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/hegemonart/get-design-done/tree/main/scripts/skill-templates/report-issue. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Report Issue?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Report Issue?

As many as you like. As long as a model supports skills, you can use Report Issue with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Report Issue AI skill free?

Yes. It is published on GitHub by hegemonart under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Grill Me

mattpocock

CommunityPopular

A relentless interview to sharpen a plan or design.

Brand Discovery

Use when a brand needs to discover or articulate its identity through structured multi-session interviews. Covers purpose, positioning, audience, personality, voice, narrative, and founder-brand…

Competitive Platform Analysis

affaan-m

CommunityPopular

Use when scoping a competitive landscape — identifying, categorising, and score-filtering a competitor set before any benchmarking begins. Decides who counts as a competitor, which tier they belong…

Frontend Slides

Create stunning, animation-rich HTML presentations from scratch or by converting PowerPoint files. Use when the user wants to build a presentation, convert a PPT/PPTX to web, or create slides for a…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

{{command_prefix}}report-issue

Pre-flight

Steps

Use through --report

Use through --force-report

Privacy contract

Troubleshooting

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now

Use through `--report`

Use through `--force-report`