encero-systems/incan / .agents/skills/create-github-issue
create-github-issue
VerifiedDrafts a GitHub issue title and body using the target repository's issue templates under .github/ISSUE_TEMPLATE. Use when the user asks to create, draft, or file a GitHub issue, bug report, feature request, chore, documentation issue, or RFC proposal, or wants issue text that matches the repo's template.
GitHub issue draft (repository templates)
Workflow
-
Identify the repository root — Use the path the user gives, or infer from context (e.g.
incan/,IncQL/). If unclear, ask which repo the issue is for. -
Discover templates — List
.github/ISSUE_TEMPLATE/*.ymlin that repository. Ignoreconfig.yml(it only configures the template picker, not form fields). -
Choose the template — Match the user's intent to a file by reading each YAML's
nameanddescription:- Bug → usually
bug_report.yml - Feature →
feature_request.yml - Refactor / CI / deps / cleanup →
chore.yml - Docs →
documentation.yml - RFC / large language or tooling change →
rfc_proposal.yml
If multiple fit or none fit, list the availablenamevalues and ask the user to pick.
- Bug → usually
-
Read the selected YAML — Parse the form from disk. Do not assume field names or area dropdowns match another repository; IncQL, Incan, and other repos differ (e.g. "Area" options).
-
Gather facts from the user or codebase — Reproduction steps, expected vs actual, versions, logs, links to files/RFCs, acceptance criteria. If the user is reporting work discovered while coding, use file paths, commands run, and error text from context.
-
Produce the draft — See Output format. For YAML
bodyblock semantics (markdown vs textarea vs dropdown vs checkboxes), use reference.md. -
Run the public text safety gate — Before showing the draft to the user or calling any GitHub issue creation/update tool, inspect the exact title and body that will be published. Public issue text must not contain local absolute paths, personal workspace paths, usernames from local paths, machine-specific temporary directories, shell prompts, or environment details that are not needed to reproduce the issue. Replace them with repo-relative paths, generic commands, or neutral placeholders.
-
Optional: related PR or branch — If the issue tracks follow-up work, mention the branch or PR link in the body where the template has a freeform section.
Public Text Safety Gate
GitHub issues are public by default and edits may remain visible in history. Treat the first publication as permanent.
Before creating or updating an issue, manually scan the title and body for these banned patterns:
- local absolute paths, including
/Users/...,/home/...,/private/...,/tmp/..., andC:\Users\... - personal workspace segments copied from a local checkout path
- commands that invoke a binary through an absolute local path
- local machine usernames, hostnames, shell prompts, or editor-specific transient paths
- private notes, agent state paths, scratch files, or temporary repro directories
Use these replacements instead:
- repo-relative paths such as
examples/session_read_transform_write_csv.incn - generic commands such as
incan run examples/session_read_transform_write_csv.incn - neutral environment descriptions such as
macOS,Linux,release/v0.3, orIncan 0.3.0-rc6 - short repro files embedded directly in the issue body when possible
If the only known command uses an absolute local path, rewrite it before publication. Do not publish first and clean it up afterward.
Fallbacks
- No
*.ymlforms — Use.github/ISSUE_TEMPLATE/*.mdif present; mirror its headings and guidance. - No templates at all — Use a minimal structure: Summary, Steps / context, Expected vs actual (bugs) or Problem, Proposal, Acceptance criteria (features), and state that the repo has no issue templates.
Output format
Return markdown the user can paste into GitHub (blank issue or “Open a blank issue”), plus metadata lines:
- Suggested title — One line. Use the YAML
titleprefix when present (e.g.bug - short subject). - Labels — If the YAML defines
labels:, list them for the user to add in the GitHub UI. - Issue type — If the YAML defines
type:(e.g. Bug, Feature), mention it for GitHub’s issue type field when applicable. - Body — For each form block in order:
- Render
markdownblocks as-is. - Render
textarea/input/dropdown/checkboxesas## {label}sections with filled content (see reference.md).
- Render
Use complete sentences. Do not leave required sections empty without calling that out.
Examples
Example: Bug (conceptual)
User: "Draft an issue for incan: the compiler crashes on empty match arms."
Steps: Open incan/.github/ISSUE_TEMPLATE/bug_report.yml, map Area / Summary / Reproduction / Output / Environment.
Fragment of output:
**Suggested title:** bug - Compiler panic on empty match arms
**Labels:** bug
## Area
- Compiler (frontend/backend/codegen)
## Summary
Expected: Typechecker or parser should report a clear diagnostic for empty match arms.
Actual: Compiler panics with ...
## Reproduction steps
1. Create `repro.incn` with ...
2. Run `incan build repro.incn`
...
Example: Feature (conceptual)
User: "Feature request for IncQL: add substrait export helper."
Steps: Use IncQL/.github/ISSUE_TEMPLATE/feature_request.yml (or the repo’s equivalent). Fill Problem statement, Proposed solution, Alternatives, Scope — using IncQL-specific areas from that file’s dropdown.
Quality checklist
- Template file was read from the correct repo;
config.ymlwas not used as the form. - Dropdown and checkbox options match that file’s YAML, not another project’s.
- Required sections are filled or explicitly flagged as missing.
- Title prefix and labels match the YAML when present.
- Public text safety gate passed on the exact issue title/body before publishing.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization. | Stars: 465k | Updated | Claude CodeCodex | Verified | Install |
| academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file). | Stars: 196k | Updated | Claude CodeCodex | Unverified | Install |
| doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |