// 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.
| name | feedback-intake |
| 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. |
This skill is the entry point for the Nimbalyst in-app feedback flow. It activates when:
/feedback:bug-report slash command/feedback:feature-request slash commandsessionType: 'bug-report' or sessionType: 'feature-request'Read the matching command file:
commands/bug-report.md in this plugincommands/feature-request.md in this pluginBoth commands share these constraints:
mcp__nimbalyst-mcp__feedback_open_github_issue without explicit user approval of the final title and body.mcp__nimbalyst-mcp__feedback_anonymize_text first, then read the output and redact anything else that looks sensitive.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.reason: 'too-long'. Fall back to: show the body in chat, open a no-body URL, tell the user to paste.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.mcp__nimbalyst-mcp__feedback_anonymize_text(text) → returns anonymized stringmcp__nimbalyst-mcp__feedback_get_environment() → app version, OS, recent error countsmcp__nimbalyst-mcp__feedback_open_github_issue({ kind, title, body }) → opens GitHub new-issue page in browser, returns { ok, opened, reason?, url? }mcp__nimbalyst-extension-dev__get_main_process_logs({ lastLines, searchTerm, logLevel, component }) → only with consentmcp__nimbalyst-extension-dev__get_renderer_debug_logs({ lastLines, searchTerm, logLevel }) → only with consentCreate diagrams and visual drawings using Excalidraw (.excalidraw files). Use when the user wants flowcharts, architecture diagrams, system diagrams, sketches, or any visual diagram. For database schemas and entity relationship diagrams, use the DataModelLM extension instead.
Create git commits using Nimbalyst's interactive commit proposal widget. ONLY use when the user explicitly clicks "Commit with AI" button or asks for "smart commit". For regular commit requests, use standard git commands instead.
Build, install, and hot-reload Nimbalyst extensions using MCP tools. Use when developing, testing, or iterating on Nimbalyst extensions.
Create structured plan documents and track work items using YAML frontmatter. Use when the user wants to plan a feature, track progress, log bugs/tasks/ideas, or organize project work.
Create visual data models for database schemas using Nimbalyst's DataModelLM editor. Use when the user wants to design a data model, database schema, entity relationship diagram, or Prisma schema.
Create visual UX mockups using HTML/CSS files (.mockup.html). Use when the user wants to design UI, wireframes, visual layouts, or plan features visually.