| name | report-neomithril-ui-issue |
| description | Create a GitHub issue for problems that appear to come from @mithrilman/neomithril-ui. Use when a consumer application reproduces a bug, styling regression, packaging problem, docs gap, or integration issue that seems attributable to this library and the user wants the issue filed in MithrilMan/neomithril-ui. |
Report Neomithril UI Issue
Create high-signal GitHub issues for @mithrilman/neomithril-ui, but triage the problem first so the issue is about the library rather than the consumer app.
Quick Checks
Run these first:
gh auth status
gh repo view MithrilMan/neomithril-ui --json nameWithOwner
If gh is unavailable or access to MithrilMan/neomithril-ui is missing, prepare a complete issue draft and tell the user they need repository access to submit it.
Triage
Before opening anything:
- Confirm the problem reproduces in the consumer app.
- Confirm the suspected fault belongs to
@mithrilman/neomithril-ui, not only to host-app code.
- Capture the installed library version from
package.json, the lockfile, or node_modules/@mithrilman/neomithril-ui/package.json.
- Capture the consumer environment that matters: React version, package manager, bundler, browser/runtime, OS.
- Search existing issues to avoid duplicates:
gh issue list --repo MithrilMan/neomithril-ui --state all --search "<keywords>"
If the issue is clearly a duplicate, link the existing issue instead of creating a new one.
Required Evidence
Every new issue should contain:
- short problem summary
- affected package version
- consumer stack details
- exact reproduction steps
- actual result
- expected result
- logs, screenshots, or inspector findings when relevant
- minimal code sample if the failure depends on usage
Prefer concise evidence over long narratives.
Create The Issue
Use a specific title, then create the issue in MithrilMan/neomithril-ui with gh issue create.
Suggested title patterns:
Button spacing collapses when ...Published styles.css misses ...Docs bootstrap fails to mention ...Theme helper generates invalid ...
Suggested command:
gh issue create --repo MithrilMan/neomithril-ui --title "<title>" --body-file <issue-body-file>
If you need to assemble the body first, create a temporary Markdown file with this structure:
## Summary
<1-3 sentence summary>
## Package Version
- @mithrilman/neomithril-ui: <version>
- react: <version>
- react-dom: <version>
## Environment
- package manager: <pnpm|npm|yarn>
- bundler/framework: <vite|next|...>
- browser/runtime: <browser or node version>
- OS: <os>
## Reproduction
1. <step>
2. <step>
3. <step>
## Actual
<what happened>
## Expected
<what should happen>
## Evidence
- <log, screenshot, inspector note, stack trace, diff, or repo snippet>
Guardrails
- Do not open an issue for app-specific code unless there is a credible library defect or docs gap.
- Do not create a vague issue with no reproduction when you can gather more local evidence first.
- Do not assume private repository access exists; check it.
- When blocked by permissions, produce a ready-to-submit issue draft instead of failing silently.
