Check Task

Did the change do what the ticket asked? Check Task compares your pending change with a Jira ticket, GitHub issue, or written spec, and returns a DONE, PARTIAL, or NOT DONE verdict with the work still missing.

Book a demo All use cases

Every requirement, checked.

Verify whether the pending change fulfills a Jira ticket, GitHub issue, or written specification. Returns a DONE, PARTIAL, or NOT DONE verdict with details of missing work.

Claude Code/cloudaeye:check-task PROJ-123

PROJ-123

Make the payment retry cap configurable

Acceptance criteria

  1. Read the retry cap from configuration.
  2. Default to 3 when the setting is missing.
  3. Reject values below 1.
  4. Document the new setting in the README.
# Task Completion Check 2 of 4 done PARTIAL
  • [x] Retry cap read from configuration Done payments/retry.ts reads RETRY_CAP
  • [x] Defaults to 3 Done Fallback applied when the setting is missing
  • [~] Values below 1 rejected Partial Rejects 0, but negative values still pass
  • [ ] Setting documented in the README Not done No README change in the diff
Gaps
  • Validate negative values, not just 0.
  • Add RETRY_CAP to the README.

Your agent asks before it edits: close these 2 gaps?

Done should
mean done.

Coding agents report tasks as finished. Check Task reads the ticket, checks each requirement against your uncommitted changes, and shows exactly what is left before anyone reviews the code.

Catch unfinished work before the PR.

Run it on your uncommitted changes and see each requirement marked done, partial, or not done, before you commit.

  • Runs onUncommitted changes
  • ChecksEach requirement
  • ReturnsA verdict and the gaps
See an example report

Check against the ticket you have.

Point it at a GitHub issue, Jira tickets, or a plain-text spec. Issues and tickets are fetched fresh on every call, so new comments count.

  • GitHub issue URLRe-fetched every call
  • Jira ticket IDsRead through your Jira app
  • Written specUsed word for word
See the commands

Never vouch for a ticket it did not read.

If a ticket cannot be resolved, you get an error, not a verdict. When a list resolves only partly, the report names what it could not read.

  • Unresolvable ticketAn error, not a verdict
  • Partly resolved listUnread tickets named
  • Mostly doneNever reported as DONE
Read the docs

Close the gaps, then check again.

When work is missing, your agent asks before it edits anything, then checks again once the gaps are closed. Ultrareview runs the same check when you name a task.

  • ReuseAsks before reusing a task
  • RecheckPicks up new issue comments
  • Ultrareviewtask:PROJ-123
See the verdicts

Three verdicts.

DONE

Every requirement in the task is met.

PARTIAL

Some requirements are met. The report lists the work that is missing.

NOT DONE

The change does not fulfill the task yet. Each gap is listed per requirement.

ERROR means the check could not run, usually because a ticket could not be resolved. It is not a judgement on your change; paste the ticket text instead.

Commands

Claude Code
/cloudaeye:check-task PROJ-123
Codex
$cloudaeye:check-task https://github.com/owner/repo/issues/42
With Ultrareview
/cloudaeye:ultrareview task:PROJ-123

Also available in Cursor, VS Code, IntelliJ IDEA, and PyCharm. Check Task runs on uncommitted changes, so there is no pull request command.