Menu
[DEPRECATED] Use agkan-review instead. Use when checking review tasks against GitHub PR status to automatically move them to done or closed.
| name | execute-review |
| description | [DEPRECATED] Use agkan-review instead. Use when checking review tasks against GitHub PR status to automatically move them to done or closed. |
DEPRECATED: This skill has been renamed. Please use
agkan-reviewinstead.Skill("agkan-review")
Workflow to retrieve tasks with Review status in agkan, check the merge/close status of GitHub PRs, and automatically update their status.
agkan task list --status review --json
Extract the PR URL from the task body in the format PR: <URL>.
If no URL is found, skip the task and output a message indicating manual verification is needed.
gh pr view <PR URL> --json state,mergedAt
| Field | Meaning |
|---|---|
state | OPEN / CLOSED / MERGED |
mergedAt | Merge date/time (null if not merged) |
| PR State | agkan Status | Command |
|---|---|---|
MERGED | done | agkan task update <id> status done |
CLOSED (mergedAt is null) | closed | agkan task update <id> status closed |
OPEN | No change | Skip (still under review) |
Retrieve all Review tasks
↓
Repeat for each task
↓
Does the body contain "PR: <URL>"?
No → Skip (output message prompting manual verification)
Yes → Check PR status
↓
What is the PR state?
MERGED → Move to done
CLOSED → Move to closed
OPEN → Skip (waiting for review)
↓
Move to next task (repeat until all tasks are processed)
PR: <URL> within the task bodydone means successful completion, closed means suspended or withdrawngh command is required and will not work in environments where it is unavailableUse when managing tasks with the agkan CLI tool - creating, listing, updating tasks, managing tags, blocking relationships, or tracking project progress with the kanban board.
Use when reviewing backlog tasks to assess decomposition, implementation readiness, and priority ordering before development begins.
Use when starting a development session to pick the highest priority Todo task from agkan, implement it directly without PR/branch, and mark it done.
Use when starting a development session to pick the highest priority Todo task from agkan, implement it, create a pull request, and mark it done.
Use when a task has been selected and you need to implement it directly without PR/branch creation - handles in_progress update, implementation, and marking done.
Use when a task has been selected and you need to implement it in an isolated (forked) context - handles in_progress update, branch creation, implementation, PR creation, and marking review.