surshar / claude-code
Claude Code is an agentic coding tool that lives in your terminal, understands your codebase, and helps you code faster by executing routine tasks, explaining complex code, and handling git workflows - all through natural language commands.
Built by Anthropic · github.com/anthropics
| @@ -30,7 +30,10 @@ | ||
| 30 | 30 | |
| 31 | 31 | **If EVENT is "issues" (new issue):** |
| 32 | 32 | |
| 33 | -4. First, check if this issue is actually about Claude Code (the CLI/IDE tool). Issues about the Claude API, claude.ai, the Claude app, Anthropic billing, or other Anthropic products should be labeled `invalid`. If invalid, apply only that label and stop. | |
| 33 | +4. First, check if this issue is actually about Claude Code. | |
| 34 | + - Look for Claude Code signals in the issue BODY: a `Claude Code Version` field or `claude --version` output, references to the `claude` CLI command, terminal sessions, the VS Code/JetBrains extensions, `CLAUDE.md` files, `.claude/` directories, MCP servers, Cowork, Remote Control, or the web UI at claude.ai/code. If ANY such signal is present, this IS a Claude Code issue — proceed to step 5. | |
| 35 | + - Only if NO Claude Code signals are present: check whether a different Anthropic product (claude.ai chat, Claude Desktop/Mobile apps, the raw Anthropic API/SDK, or account billing with no CLI involvement) is the *subject* of the complaint, not merely mentioned for context. If so, apply `invalid` and stop. If ambiguous, proceed to step 5 WITHOUT applying `invalid`. | |
| 36 | + - The body text is authoritative. If a form dropdown (e.g. Platform) contradicts evidence in the body, trust the body — dropdowns are often mis-selected. | |
| 34 | 37 | |
| 35 | 38 | 5. Analyze and apply category labels: |
| 36 | 39 | - Type (bug, enhancement, question, etc.) |
| @@ -67,4 +70,5 @@ | ||
| 67 | 70 | - Be conservative with lifecycle labels — only apply when clearly warranted |
| 68 | 71 | - Only apply lifecycle labels (`needs-repro`, `needs-info`) to bugs — never to questions or enhancements |
| 69 | 72 | - When in doubt, don't apply a lifecycle label — false positives are worse than missing labels |
| 70 | -- It's okay to not add any labels if none are clearly applicable | |
| 73 | +- On new issues (EVENT "issues"), always apply exactly one of `bug`, `enhancement`, `question`, `invalid`, or `duplicate`. If unsure, pick the closest fit — an imperfect category label is better than none. | |
| 74 | +- On comment events, it's okay to make no changes if nothing applies. |