// Interact with the Fizzy tracker for Pagecord work. Use when the user asks to list, create, update, move, close, comment on, or inspect Fizzy cards or boards.
Investigate and fix a Sentry issue in this codebase. Use when the user provides a Sentry issue URL or ID and wants diagnosis, a fix, verification, or a PR.
Run the local CI sequence for this repo. Use when the user asks to run CI, verify a branch before push, or check code quality with the full local pipeline.
Interact with the Pagecord API for a blog. Use when the user wants to inspect posts or pages, publish content through the API, check API connectivity, or inspect the home page.
Interact with Cloudflare R2 buckets used by Pagecord. Use when the user wants to list objects, inspect bucket stats, fetch files, or check backup integrity in R2.
Investigate a customer support email and draft a reply. Use when the user pastes a customer message, bug report, billing question, feature request, or how-to question.
Interact with the Pagecord API - list posts/pages, publish content, and manage blog resources. Usage: /pagecord <command> [args]
| name | fizzy |
| description | Interact with the Fizzy tracker for Pagecord work. Use when the user asks to list, create, update, move, close, comment on, or inspect Fizzy cards or boards. |
Use the Fizzy API via curl.
FIZZY_TOKEN from /Users/olly/dev/pagecord/.env.https://app.fizzy.doGET /my/identity and reuse it for the rest of the task.Every API call should include:
Authorization: Bearer $TOKENAccept: application/jsonContent-Type: application/json for write requestsCard descriptions should be sent as HTML, not Markdown. Fizzy stores the description
through ActionText; Markdown is shown as plain text, while HTML renders correctly in
description_html. Use standard tags such as <h2>, <p>, <ul>, <li>, and
<code>. Avoid task-list checkbox inputs in descriptions because ActionText strips
the <input> elements.
GET /$SLUG/boardsGET /$SLUG/boards/:board_id/columnsGET /$SLUG/cardsGET /$SLUG/cards/:card_numberPOST /$SLUG/boards/:board_id/cards with {"card":{"title":"...","description":"..."}}PUT /$SLUG/cards/:card_numberPOST /$SLUG/cards/:card_number/triage with {"column_id":"..."}POST /$SLUG/cards/:card_number/commentsPOST /$SLUG/cards/:card_number/closureDELETE /$SLUG/cards/:card_number/closureIf the user does not specify a board for creation, list boards first. If the user wants a move but does not specify a column, list columns for that board first.
For card lists, show a concise table with number, title, status, tags, and board. For single-card reads, summarize the key fields instead of dumping raw JSON.