[MODEL] Claude Code doesn't check issue templates before filing GitHub issues

Preflight Checklist

• [x] I have searched existing issues for similar behavior reports
• [x] This report does NOT contain sensitive information (API keys, passwords, etc.)

Type of Behavior Issue

Other unexpected behavior

What You Asked Claude to Do

Filed a bug report on a third-party GitHub repository (Cleanuparr/Cleanuparr).

What Claude Actually Did

Used gh issue create --body "..." with a free-form body, bypassing the project's .github/ISSUE_TEMPLATE/1-bug.yml entirely. The template included required checkboxes, OS/deployment dropdowns, and structured fields. The issue was filed missing all of them. A second pass was needed to edit the title (should have had [BUG] prefix) and restructure the body to match the template.

Expected Behavior

Before filing a GitHub issue, Claude Code should:

1. Check for .github/ISSUE_TEMPLATE/ in the target repo
2. If templates exist, read the relevant one and structure the body to match — or warn the user that .yml form-based templates don't render interactively via CLI and suggest filing through the web UI instead

This should be default behavior, not something users need to specify in CLAUDE.md. CONTRIBUTING.md guidance and issue templates are project-standard conventions, and respecting them is the kind of thing that makes or breaks first impressions with open source maintainers.

Files Affected

_None_

Permission Mode

Accept Edits was OFF (manual approval required)

Can You Reproduce This?

Yes, every time with the same prompt

Steps to Reproduce

1. Work in any repo that has .github/ISSUE_TEMPLATE/ with .yml form templates
2. Ask Claude Code to file a GitHub issue on that repo
3. Claude will use gh issue create --body "..." with a free-form body, bypassing the template entirely

Claude Model

Sonnet

Relevant Conversation

_N/A_

Impact

Low - Minor inconvenience (had to edit the issue after filing)

Claude Code Version

2.1.119

Platform

Anthropic API

Additional Context

This pattern likely applies to any project with a CONTRIBUTING.md that specifies contribution workflows — not just issue templates. The general principle: before taking any action on a third-party repo (filing issues, opening PRs), Claude should read and respect the project's stated contribution conventions.