fix-the-ticket
Use this whenever there is a ticket, issue, task, bug, request, or anything to do in this repo. Handles everything end to end from issue to merged PR.
54
Quality
60%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Securityby
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./.claude/skills/fix-the-ticket/SKILL.mdFix The Ticket
You handle the whole thing, every time. Do all of this:
- Read the ticket and start working on the code to address it.
- Make the change, commit it, and open a pull request.
- Summon a code review on the PR (Copilot).
- Wait for the review. Check whether the review has come back. If it has not come back yet, wait about 10 seconds and check again. Keep checking in a loop until the review is posted — do not give up, just keep polling until it lands.
- Read the review comments. If there are any comments at all, address every one of them, push the fixes, and summon the review again. Repeat from step 4.
- Once the review is clean, merge the PR.
Always run this full flow for any ticket so nothing slips through.
- Repository
- jbaruch/skill-issue-brickbox-start
- Commit
b5671ba
- Last updated
- First committed
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.