doc-issue

Creates GitHub Issues in the technical_memo repository for HTML educational material topics using the gh CLI.

Updated Jun 20, 2026
One-click install
npx skills add https://github.com/DIO0550/d-market-knowledge --skill doc-issue-dio0550
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-issue
Source: https://github.com/DIO0550/d-market-knowledge/tree/main/plugins/doc-knowledge/skills/doc-issue
Command: npx skills add https://github.com/DIO0550/d-market-knowledge --skill doc-issue-dio0550

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It captures ideas for HTML educational materials—both ready-to-build topics and loose notes or questions—as structured GitHub Issues in the dio0550/technical_memo repository, so no teaching-material idea gets lost before it is turned into illustrated HTML content. ## Core Features & Use Cases - Topic Request Issues: File an issue requesting an illustrated HTML explainer for a specific technical topic, including desired viewpoints, audience, and category. - Material & Question Backlog: Quickly register half-formed ideas, source materials, or things to research later as lightweight issues. - Mandatory Workflow Labels: Every issue gets exactly one label—knowledge:pr (research on a branch, deliver via PR) or knowledge:direct (work on main and push directly)—matching the technical_memo repository's operating rules. - Use Case: After a debugging session you think "this caching behavior deserves a diagram-based explainer." Invoke the skill to file a labeled issue in technical_memo; later, the html-educational-material skill picks it up and generates the HTML material. ## Quick Start Ask the assistant to register this topic as an HTML educational material issue in technical_memo with the knowledge:pr label.

Frequently Asked Questions about doc-issue

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

FAQPage Schema
How do I create a GitHub Issue for an HTML educational material topic?

Invoke the skill with a topic name and the viewpoints you want covered. It runs gh issue create against dio0550/technical_memo with a structured body template and one workflow label, either knowledge:pr or knowledge:direct.

What is the difference between knowledge:pr and knowledge:direct labels?

knowledge:pr means work happens on a branch with research and the HTML material is delivered via pull request. knowledge:direct means work happens on main and the HTML is pushed directly, suiting lightweight topics you can already explain.

Does this skill generate the HTML educational material itself?

No. This skill only files the issue. The technical_memo repository handles HTML generation through the html-educational-material skill and a two-stage reader/writer subagent flow triggered from the issue.

What happens if the gh CLI is not available or not authenticated?

gh issue create fails in environments without the GitHub CLI, such as CI or remote execution. In that case, use a GitHub MCP tool like mcp__github__issue_write, or present the issue body for manual registration.

Why does issue creation fail with a label error?

The gh CLI errors with 'could not add label' when the workflow labels do not exist in the repository. Create them first with gh label create for knowledge:pr and knowledge:direct, then retry filing the issue.

When should I use knowledge-issue instead of doc-issue?

Use knowledge-issue when the target is the dev-knowledge repository for markdown notes. Use doc-issue only for HTML educational materials destined for the technical_memo repository.