# Feedback Intake

Help the user file a bug report or feature request for Nimbalyst.

- Repository: https://github.com/nimbalyst/nimbalyst (2013 stars)
- Category: Git and review
- License: MIT
- Last updated: 2026-10-31
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add nimbalyst/nimbalyst --skill feedback-intake -g -a claude-code -y`
Codex: `npx skills add nimbalyst/nimbalyst --skill feedback-intake -g -a codex -y`
Cursor: `npx skills add nimbalyst/nimbalyst --skill feedback-intake -g -a cursor -y`
Gemini CLI: `npx skills add nimbalyst/nimbalyst --skill feedback-intake -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add nimbalyst/nimbalyst`

## Description

Help the user file a bug report or feature request for Nimbalyst. Activates when the user opens the in-app feedback flow or runs /feedback:bug-report or /feedback:feature-request. Coordinates evidence gathering, anonymization, and posting to GitHub Issues.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Nimbalyst Feedback Skill

This skill is the entry point for the Nimbalyst in-app feedback flow. It activates when:

- The user runs the `/feedback:bug-report` slash command
- The user runs the `/feedback:feature-request` slash command
- The user opens a session with `sessionType: 'bug-report'` or `sessionType: 'feature-request'`

## Behavior

Read the matching command file:
- For bug reports: `commands/bug-report.md` in this plugin
- For feature requests: `commands/feature-request.md` in this plugin

Both commands share these constraints:

1. **The user is the gate.** Never call `mcp__nimbalyst-situational__feedback_open_github_issue` without explicit user approval of the final title and body.
2. **Anonymize aggressively.** Run anything that includes file paths, log content, environment strings, or workspace identifiers through `mcp__nimbalyst-situational__feedback_anonymize_text` first, then read the output and redact anything else that looks sensitive.
3. **Honor the intake flags.** Bug-report sessions include `Log gathering: allowed` or `Log gathering: not allowed`; feature-request sessions may include `UX mockup: requested` or `UX mockup: not requested`. Only bug reports may read logs, and only when log gathering is allowed.
4. **Handle long reports.** When the drafted body exceeds the URL safe length, the URL builder returns `reason: 'too-long'`. Fall back to: show the body in chat, open a no-body URL, tell the user to paste.
5. **Target repo and templates.** Bug reports use `bug_report.yml`; feature requests use `feature_request.yml`. Both target `nimbalyst/nimbalyst`. Don't hardcode the URL, let the URL builder handle template selection and field-id routing. The GitHub issue type (Bug / Feature) and `status:needs-triage` label come from the template frontmatter, not from the URL builder.

## Tools available

The rest: https://github.com/nimbalyst/nimbalyst/blob/HEAD/packages/extensions/feedback/claude-plugin/skills/feedback-intake/SKILL.md