resolve-issue

name	resolve-issue
description	Resolve a Vivliostyle.js GitHub issue end-to-end. Use when: reproducing a bug, fixing an issue, creating test case from issue, verifying issue behavior, debugging rendering problems. Fetches issue content, creates an HTML test file, reproduces the bug visually with the VS Code integrated browser, and falls back to Chrome DevTools MCP when DevTools-specific diagnostics are needed.
argument-hint	GitHub issue number or URL (e.g. #1879 or https://github.com/vivliostyle/vivliostyle.js/issues/1879)

Resolve a Vivliostyle.js Issue

Fetch a GitHub issue, create a minimal test case, visually confirm the bug, fix the code, and verify the fix using the dev server and the VS Code integrated browser. Use Chrome DevTools MCP only when you need DevTools-specific diagnostics.

Procedure

1. Fetch the Issue

• Parse the issue number from the user's input (e.g., #1879, 1879, or a full GitHub URL).
• Use the github-pull-request_issue_fetch tool to fetch the issue content (owner: vivliostyle, repo: vivliostyle.js).
• Extract the following from the issue body:
  • Test HTML: Look for HTML code blocks, embedded test cases, or links to reproducible examples.
  • Expected vs actual behavior: Understand what the bug is.
  • CSS properties or features involved: Identify the area of the engine affected.

2. Create the Test File

• Create an HTML test file in packages/core/test/files/.
• File naming: Use kebab-case derived from the issue topic, e.g., , . Only add the issue number if the name would otherwise collide with an existing file (e.g., ).