Asking tasksmind Directly

Every @tasksmind mention command: instant answers on PR and ticket status, and agent commands that review, summarize, fix, and implement.

Not every use of tasksmind starts with a customer report. @mention it in any channel it’s in, or just DM it, and it runs the same commands either way.

Instant answers

No agent job, no wait, just a reply in the thread.

Command	What it does
@tasksmind status PR #214	PR status, review state, and CI checks
@tasksmind status TICKET-123	Jira ticket status and execution history
@tasksmind changes PR #214	File changes and diff summary for a PR

Agent commands

These start a background job and stream progress in a thread. Anything that would change code (implement, fix bug, fix CI) waits on the same approval card before committing or opening a PR. It never auto-merges without that approval.

Command	What it does
@tasksmind review PR #214	Full code review: findings, risks, suggestions
@tasksmind fix CI for PR 214	Fetch failing check logs, identify root cause, propose fix
@tasksmind fix bug <description>	Investigate a bug report, find root cause, propose fix
@tasksmind implement <feature>	Plan and implement a feature (requires approval before committing)
@tasksmind summarize this repo	Index the connected repo and generate an architecture summary
@tasksmind investigate <topic>	Pull Slack, logs, and recent commits to root-cause an issue

What it looks like

#eng

Priya · 9:14 AM @tasksmind summarize this repo

tasksmind · 9:15 AM Indexed the repo. It’s a Vite + React frontend backed by Supabase edge functions, with a Python worker layer handling the Slack agent and fix generation. Full breakdown in the thread.

Priya · 9:20 AM @tasksmind review PR #214

tasksmind · 9:21 AM Reviewed. One risk worth flagging: the new retry logic doesn’t cap attempts, could loop under sustained failure. Two minor suggestions in the thread.

Fixing a failing CI run

The same fix-CI command, in depth.

See everything tasksmind can do

Back to the full use-case index.