get_next_actionable_page workflow
Get the highest-priority page with unresolved issues
Overview
After comparisons complete, this tool returns the most important page that still has unresolved issues — ordered by backlink rank. Use it to iteratively fix pages in priority order: get next page → fix issues → log attempts → re-compare → repeat. Also returns an architecture block (shared_elements with behaviors and nav_items, routes, content_types, design_systems, component_styles) so you have full site context without extra tool calls.
How It Works
- Queries compared pages in the job with open issues, sorted by backlink importance.
- Returns the highest-priority page with all its open issues, sorted by severity.
- Includes attempt history, code suggestions, latest_user_status, and resolution_reason per issue.
- Supports skip_page_ids to move through pages you've already addressed.
- When all compared pages are clear, surfaces the top-priority error-status page instead.
- Returns a complete workflow guide for fixing, logging, verifying, and moving to the next page.
Input Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
job_id |
string |
required | Cloning job ID |
skip_page_ids |
string[] |
optional | Page IDs to skip (pages already fixed in this session) |
include |
string[] |
optional | Architecture facets to include: shared_elements, routes, content_types, design_systems, component_styles. Omit for all five; pass [] to skip the architecture block entirely. |
What You Get Back
- Page details (URL, type, match scores, backlink rank)
- All open issues sorted by severity with before/after values, latest_user_status, and resolution_reason
- Attempt history per issue
- Architecture block: shared elements with behaviors and nav_items, routes, content types, design systems, component styles
- Workflow instructions for fixing, logging, verifying, and moving to the next page
Example Use Case
After run_full_comparison finishes, call get_next_actionable_page to get the most important page needing fixes. Fix the critical issues, call log_fix_attempt, then call compare_page_pair to re-verify. Repeat with the next page.
Tips
Start with the first page returned — it's the highest priority based on backlink importance.
Use skip_page_ids to track pages you've already handled in the current session.
Focus on critical and high severity issues first within each page.
If stuck on an issue after 3+ attempts, use diagnose_fix for AI-powered root cause analysis.
To mark an acceptable difference as intentional, call mark_issue with action: 'resolved' and a descriptive reason.
Pass include=[] to skip the architecture block and reduce response size.