bootspring_feedback
Submit feedback, report issues, and request features for Bootspring.
Overview#
The bootspring_feedback tool enables you to submit feedback directly to the Bootspring team. Report bugs, request features, share suggestions, or provide general feedback about your experience.
Parameters#
| Parameter | Type | Required | Description |
|---|---|---|---|
type | string | Yes | Feedback type: bug, feature, suggestion, general |
message | string | Yes | Your feedback message |
context | object | No | Additional context |
Feedback Types#
| Type | Description |
|---|---|
bug | Report a bug or issue |
feature | Request a new feature |
suggestion | Suggest an improvement |
general | General feedback |
Context Object#
| Field | Type | Description |
|---|---|---|
tool | string | Related tool name |
agent | string | Related agent name |
workflow | string | Related workflow |
error | string | Error message if applicable |
version | string | Bootspring version |
Usage Examples#
Report a Bug#
Use the bootspring_feedback tool with:
- type: "bug"
- message: "Quality gate fails silently when eslint config is missing"
- context: { tool: "bootspring_quality", error: "Config not found" }
Response:
Loading code block...
Request a Feature#
Use the bootspring_feedback tool with:
- type: "feature"
- message: "Add support for Bun as a package manager"
Response:
Loading code block...
Suggest an Improvement#
Use the bootspring_feedback tool with:
- type: "suggestion"
- message: "The database-expert agent could include more NoSQL examples"
- context: { agent: "database-expert" }
General Feedback#
Use the bootspring_feedback tool with:
- type: "general"
- message: "Really enjoying the workflow feature - it's improved our team productivity"
Response Format#
Success Response#
Loading code block...
Error Response#
Loading code block...
Feedback Categories#
Bug Reports#
When reporting bugs, include:
- Steps to reproduce
- Expected behavior
- Actual behavior
- Error messages
- Environment details
Use the bootspring_feedback tool with:
- type: "bug"
- message: "Steps: 1. Run quality gate 2. Expected: lint errors shown 3. Actual: silent failure"
- context: {
tool: "bootspring_quality",
error: "ENOENT: no such file or directory",
version: "1.1.0"
}
Feature Requests#
When requesting features, describe:
- The problem you're trying to solve
- Your proposed solution
- Expected benefits
Use the bootspring_feedback tool with:
- type: "feature"
- message: "Problem: Need to track breaking changes. Solution: Add a changelog generator agent. Benefit: Automated release notes."
Suggestions#
For improvements:
- What currently works
- What could be better
- Specific ideas
General Feedback#
Share your experience:
- What you like
- What helped you
- Use cases
Anonymous vs Identified#
Feedback can be:
- Anonymous: No identifying information attached
- Identified: Linked to your account for follow-up
By default, feedback includes:
- Bootspring version
- OS platform
- Node.js version
It does NOT include:
- Project code
- File contents
- Personal data (unless provided)
Privacy#
Your feedback is handled according to our privacy policy:
- Feedback is used to improve Bootspring
- No code or sensitive data is collected
- Context information is optional
- You can request deletion of feedback
Best Practices#
Be Specific#
Include details that help us understand and address your feedback:
- Version numbers
- Error messages
- Steps to reproduce
Provide Context#
Use the context parameter to give us relevant information:
- Which tool or agent
- What workflow
- What you were trying to do
Check Existing Issues#
Before submitting, check if similar feedback exists:
Related Tools#
- bootspring_help - Get help before submitting feedback
- bootspring_status - Check system status
- bootspring_upgrade - Check for updates that may resolve issues