check-blocked

To unblock project board issues automatically, this skill paginates through the Blocked column, reads issue bodies and comments for referenced dependencies, and re-triages items by applying status transitions once all dependencies are closed.

The best way to re-triage blocked issues is to scan the entire Blocked column with pagination, ensuring no item is missed, and update statuses by verifying that every referenced dependency in the issue body and comments is fully closed.

Issue dependency identification works by parsing the text of issue bodies and their comments to find references such as "blocked by #X" or "depends on repo#Y", then checking the resolution status of those linked dependencies before re-triaging.

Yes, you can use this triage process for multi-page project boards. It explicitly paginates through all pages of the Blocked column to evaluate every blocked issue, ensuring comprehensive coverage before applying any status updates.

You should not use automated re-triage if your blocked issues lack clear textual dependency references like "blocked by #X" in their bodies or comments, as the tool requires these explicit links to verify resolution and apply transitions.