Skip to content

Instantly share code, notes, and snippets.

@jscalo
Created July 6, 2026 15:46
Show Gist options
  • Select an option

  • Save jscalo/39e0217214310549d1b6231bf81df95d to your computer and use it in GitHub Desktop.

Select an option

Save jscalo/39e0217214310549d1b6231bf81df95d to your computer and use it in GitHub Desktop.
My CLAUDE / AGENTS setup for Taska MCP
[comment]: <> (Taska is an issue tracking Mac app from Leitmotif. You can get it here: https://taska.now)
## Tickets & Issues
### Setup
- Use the Taska MCP server to file and read tickets, but only when told to do so.
- The <your-project> repo is "<your-repo>".
- Writes require "Allow Write Access" on in Taska › Settings › Extensions; this is enabled.
### Creating Tickets
- Before creating, list/search existing issues to avoid duplicates.
- When looking at an existing issue, also read its comment history using list_comments.
- Leaving high-value comments on an issue is OK. Use add_comment.
- Use Taska's "Fruit Co" (aka Apple's) priority system: P1 → P2 → P3 → P4 = Showstopper → Important → Expected → Nice to Have
- If a milestone isn't specified, default to the Claude milestone
- Specify repro steps when applicable: Steps 1, 2 ,3, ..., what was expected, what happened instead.
- Use labels. This repo's labels are:
- bug
- documentation
- duplicate
- enhancement
- good first issue
- help wanted
- invalid
- question
- wontfix
- in progress
- to verify
("Priority labels" from above are Showstopper, Important, Expected, Nice to Have)
### Working on Tickets
- Grab open tickets as instructed but avoid tickets with the 'in progress' and 'to verify' labels (unless you are a verifier).
- When grabbing a ticket to work on, apply the 'in progress' label. Remove that label when done (whether you close it or not).
- When done fixing the issue from the ticket:
- add a comment with what you did and how it addressed the issue
- commit to the current branch with a good commit message
- remove the 'in progress' label
- add the 'to verify' label
### Verifying Tickets
- If you are asked to verify tickets, look for tickets with the 'to verify' label, grab it, and add the 'in progress' label.
- Verify that the fixing agent's work is correct
- If correct:
- remove 'to verify' and remove 'in progress' labels
- add the 'verified' label
- close the ticket
- If not correct:
- add a comment explaining why the work wasn't correct
- remove the 'to verify' and 'in progress' labels
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment