resolve-qa

You can automate Notion QA issue updates by passing a Notion permalink or LK-ID to the resolve-qa skill. It retrieves the page, analyzes context, prepares the branch or worktree, updates the page status, and leaves contextual comments via the Notion API.

Yes, providing a Notion URL triggers the workflow to parse the issue context and guide you through branch selection for fixes. It prepares the relevant worktree so you can start fixing the bug immediately after the page is retrieved.

Leaving contextual comments on Notion pages is fully supported using the Notion API create-a-comment interaction. After analyzing the issue media and context, the skill posts relevant comments directly to the Notion page to document the resolution.

The best way to manage QA issue resolution is using an automated workflow that links Notion page updates with git branch preparation. This skill handles page retrieval, status patching, and worktree setup to streamline the entire QA process end-to-end.

To update a Notion QA page status after preparing a fix branch, run the resolve-qa command again with the same argument. It executes a Notion API patch operation to update the page status once the relevant branch and worktree are ready.

You need to provide an LK-ID or Notion permalink because the skill uses it as the entry point to retrieve the specific QA page via the Notion API. Without this identifier, the skill cannot parse the context or initiate the branch preparation workflow.