Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [MODEL] Claude Code doesn't check issue templates before filing GitHub issues [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#53104•Fetched 2026-04-25 06:12:14
View on GitHub
Comments
1
Participants
2
Timeline
1
Reactions
0
Author
MikeTheCanuckMikeTheCanuck
Participants
dengluozhangdengluozhangMikeTheCanuckMikeTheCanuck
Timeline (top)
commented ×1

Error Message

  1. 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
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues for similar behavior reports
  • 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.

extent analysis

TL;DR

To fix the issue, Claude Code should be updated to check for and respect .github/ISSUE_TEMPLATE/ in target repositories before filing issues.

Guidance

  • Check if the target repository has a .github/ISSUE_TEMPLATE/ directory and read the relevant template to structure the issue body accordingly.
  • If the template is in .yml form, warn the user that it doesn't render interactively via CLI and suggest filing through the web UI instead.
  • Update Claude Code to default to respecting project-standard conventions, such as issue templates and CONTRIBUTING.md guidance.
  • Test the updated behavior by filing an issue on a repository with a .github/ISSUE_TEMPLATE/ directory.

Example

No code snippet is provided as the issue does not imply a specific code change.

Notes

This fix may require updates to the Claude Code's issue filing mechanism to handle different types of issue templates and contribution conventions.

Recommendation

Apply a workaround by manually checking for and respecting issue templates and contribution conventions when filing issues on third-party repositories, until an updated version of Claude Code is available that defaults to this behavior.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#ssr#docker error#permission error#memory optimization

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING