" \ --label "kumo-coding-agent,<type-label>" \ --assignee "manushmurali-kumo" \ --body "<body>" ``` Use a heredoc for the body to preserve formatting. If `gh` is not authenticated, tell the user to run `gh auth login -h github.com` first and provide the exact command to retry. ### Step 7: Follow Up After the issue is created: 1. Print the issue URL 2. Tell the user: "Your issue has been filed. A Kumo team member will review it and follow up with you." 3. If the type is **gap**, suggest also adding an entry to `context/_gaps.yaml` with status: open 4. If the type is **bug** and the fix is obvious, suggest running `/kumo-pr` to fix it directly --- > Source: [kumo-ai/kumo-coding-agent](https://github.com/kumo-ai/kumo-coding-agent) — distributed by [TomeVault](https://tomevault.io). <!-- tomevault:4.0:skill

# Kumo Issue > File a GitHub issue on the kumo-coding-agent repo to report a gap, bug, or feature request for the Kumo data science agent (context docs, skills, or verticals). Use when someone says "report a problem with the agent", "the agent got something wrong", "file an issue", or "request a new skill". Use when this capability is needed. - Skill: `tomevault-io/kumo-issue` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/kumo-issue` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/kumo-issue/raw - Safety review: pending (external: skill-scanner PASS, skillspector PASS) - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: AI & ML - Author: tomevault-io (https://skillmd.com/u/tomevault-io) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/tomevault-io/kumo-issue --- # File a kumo-coding-agent Issue Create a structured GitHub issue on kumo-ai/kumo-coding-agent for agent gaps, bugs, or feature requests. **This command works in both Claude Code (interactive) and Codex (headless).** In Codex, provide a description as the argument — interactive prompting is not available. **User input:** $ARGUMENTS ## Instructions ### Step 1: Validate GitHub CLI Auth Run: ```bash gh auth status ``` If `gh` is not authenticated, tell the user to run `gh auth login -h github.com` first and stop before gathering more information. ### Step 2: Gather Information If `$ARGUMENTS` is provided, parse it to understand the issue. If `$ARGUMENTS` is empty, ask the user these questions (skip in headless mode): 1. What happened? (What were you trying to do?) 2. Which skill or context doc was involved? (If known) 3. What did you expect vs what happened? ### Step 3: Classify the Issue Determine the type based on the description: | Type | Signal | Label | |------|--------|-------| | **gap** | "agent didn't know", "missing info", "couldn't answer" | `gap` | | **bug** | "wrong info", "incorrect", "outdated", "says X but should be Y" | `bug` | | **feature** | "add support for", "new skill", "new vertical", "would be nice" | `enhancement` | ### Step 4: Identify Affected Files Search for files related to the issue: ```bash grep -rl "" context/ skills/ ``` If the user mentioned a specific file, verify it exists and note the relevant section. Also check if this is already tracked: ```bash grep -i "" context/_gaps.yaml ``` If already tracked, tell the user and ask if they still want to file an issue. ### Step 5: Compose the Issue **Title format:** `kumo: ` Examples: - `kumo: missing Databricks Unity Catalog connector docs` - `kumo: pql-syntax.md lists MODE as valid aggregation` - `kumo: add healthcare/clinical trials vertical` **Body template:** ```markdown ## Type ## Affected File(s) - `` (line ~N) ## Description ## Expected Behavior ## Current Behavior ## Suggested Fix ## Context --- *Filed via `/kumo-issue` by @REPORTER* ``` ### Step 6: Create the Issue First, capture the reporter's GitHub identity: ```bash gh_user=$(gh api user --jq '.login') ``` Replace `@REPORTER` in the body template with `@$gh_user`. Run: ```bash gh issue create \ --repo kumo-ai/kumo-coding-agent \ --title "" \ --label "kumo-coding-agent,<type-label>" \ --assignee "manushmurali-kumo" \ --body "<body>" ``` Use a heredoc for the body to preserve formatting. If `gh` is not authenticated, tell the user to run `gh auth login -h github.com` first and provide the exact command to retry. ### Step 7: Follow Up After the issue is created: 1. Print the issue URL 2. Tell the user: "Your issue has been filed. A Kumo team member will review it and follow up with you." 3. If the type is **gap**, suggest also adding an entry to `context/_gaps.yaml` with status: open 4. If the type is **bug** and the fix is obvious, suggest running `/kumo-pr` to fix it directly --- > Source: [kumo-ai/kumo-coding-agent](https://github.com/kumo-ai/kumo-coding-agent) — distributed by [TomeVault](https://tomevault.io).