From trello-cli
Use when user says "file a bug for that", "create a ticket", "that's a bug - capture it", or wants to record an issue for later work
How this skill is triggered — by the user, by Claude, or both
Slash command
/trello-cli:file-bugThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Capture current session context into a Trello card so work can continue later. Returns just the card reference - keeps context minimal.
Capture current session context into a Trello card so work can continue later. Returns just the card reference - keeps context minimal.
YOU saw the issue - YOU describe it. Don't ask the user what happened.
Collect:
Description template:
## Steps to Recreate
1. [What was being done]
2. [What action triggered it]
## Expected Behavior
[What should have happened]
## Actual Behavior
[What actually happened]
## Notes
[Any additional context - file paths, config, etc.]
Attachments:
stacktrace.txtscreenshot.pngbin/trello card new "Bug: <concise title>" \
--description "<formatted description>" \
--label bug \
--position top
If attachments exist:
bin/trello attach upload <card-ref> <file>
Report ONLY: "Filed as # - "
Nothing more. Don't fill context with card details.
If you catch yourself doing these, STOP:
| Phase | Action | Output |
|---|---|---|
| 1. Gather | Collect error, steps, expected/actual | Context in memory |
| 2. Format | Apply template, handle attachments | Description + files |
| 3. Create | Run CLI commands | Card created |
| 4. Confirm | Report reference | "Filed as #47" |
npx claudepluginhub mjbellantoni/cc-marketplace --plugin trello-cliTransforms error logs, screenshots, voice notes, and rough bug reports into structured GitHub issues with reproduction steps, impact, and evidence.
Captures user-reported bugs as durable GitHub issues using the project's own domain language. Avoids stale references like file paths.
Takes a free-form bug report, localises the suspected code, captures a reproducer, and emits a groomed bug task with a regression-test acceptance criterion. Trigger when a user reports a bug or pastes a stack trace.