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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 6.0 KB |
| reference.md | markdown | 1.9 KB |
reference.md
View on GitHub# GitHub issue template mapping (YAML forms)
Repositories that use [issue forms](https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms) store them under `.github/ISSUE_TEMPLATE/` as `*.yml` files.
## Files to skip
- **`config.yml`** — Chooses which templates appear in the picker; it is not a form.
- **`PULL_REQUEST_TEMPLATE*`** — Belongs to PRs, not issues.
## Top-level keys (useful for output)
| Key | Use |
|-----|-----|
| `name` | Human-readable template name (picker label). |
| `description` | Short blurb; helps pick the right template. |
| `title` | Default title **prefix** (e.g. `bug - `); suggest full title = prefix + concise subject. |
| `labels` | Optional list; tell the user to apply these when opening the issue. |
| `type` | Optional GitHub issue type (if the repo uses issue types). |
## `body` block types
For each item in `body:`:
| `type` | Output |
|--------|--------|
| `markdown` | Include `attributes.value` as normal markdown (intro, links, policy). |
| `textarea` / `input` | Section `## {label}` then filled prose. Use `description` as a hint for what to write. |
| `dropdown` | Section `## {label}` then chosen option(s). If `multiple: true`, use a bullet list. |
| `checkboxes` | Section `## {label}` then `- [x]` / `- [ ]` per option from user intent; respect `required` on options when the user confirms. |
If `validations.required: true` and the user gave no content, note that the section must be completed before submit.
## No YAML forms
If the repo only has `.github/ISSUE_TEMPLATE/*.md` (legacy templates), read the file and mirror its sections and any HTML comments that describe fields.
## Blank issues
If `blank_issues_enabled: true` in `config.yml`, a single markdown body built from the YAML is valid for a blank issue; remind the user to set title and labels manually to match the template.
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: 466k | 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 |