Menu
Quickly captures a bug, feature request, or improvement as a structured GitHub issue without interrupting the user's development flow. Use when the user needs to log something fast while staying focused on current work.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | create-issue |
| description | Quickly captures a bug, feature request, or improvement as a structured GitHub issue without interrupting the user's development flow. Use when the user needs to log something fast while staying focused on current work. |
This skill captures a bug, feature request, or improvement as a complete, well-structured GitHub issue — fast. The user is mid-development and wants to capture an idea without losing their flow.
/hyper-create-issue.Ask Targeted Questions The user is mid-flow — be concise. Use AskUserQuestion to collect issue type and priority without multiple back-and-forths:
What type of issue is this?
- Option A: Bug — something is broken or behaving incorrectly
- Option B: Feature request — new functionality desired
- Option C: Documentation — docs are missing or incorrect
- Option D: Chore / maintenance — tech debt, refactor, or infra work
Then use AskUserQuestion for priority (if not obvious from context):
What priority should this issue have?
- Option A: Critical — blocking, needs immediate attention
- Option B: High — important, should be addressed soon
- Option C: Medium — normal backlog item
- Option D: Low — nice-to-have, no urgency
For any remaining gaps (current vs. desired behavior, specific symptoms), ask inline in the same message.
Search for Context
spec/compiled/architecture.yml to identify the specific node_ids that this issue will affect.Draft the Issue Create a complete issue with:
node_ids from the hypergraph (max 3)bug/feature/improvement), priority (high/normal/low), effort (small/medium/large)Create the Issue
Use the shell to run gh issue create with the drafted content, or output the issue body for the user to copy if GitHub CLI is unavailable.
normal, effort: medium (ask only if unclear).Updates all project documentation after code or skill changes. Always reads actual implementation before writing. Covers README, CHANGELOG, docs/, AGENTS.md, memory files, and skills-info.md. Use after completing any feature, fix, refactor, or skill update.
Compacts the current conversation into a handoff document so a fresh agent can continue the work. Saves to the OS temp directory, not the workspace. Pass an optional argument describing what the next session will focus on.
Documents the process, methodology, and decisions of the current session as a reproducible narrative. Saves to spec/process/ in the workspace so the journey can be understood and recreated by others.
Scaffolds a new project by conducting an interview to collect metadata and generating standard repository documentation files from the framework templates. Use when setting up a new repository.
Run this after /hyper-tutorial-run to turn tutorial failures into a structured, constraint-aware goal prompt. Interviews the user about their goal and what may/may not be changed, then generates a paste-ready prompt for a new Claude Code fix session. Does NOT re-run tutorial commands.
Generates a markdown tutorial from an integration test or user-provided files through iterative LLM + human collaboration. Tutorials are saved to tutorials/<name>/ with organized supporting files.