resolve-qa

Update Notion QA pages and add comments after preparing worktrees.

5|7|Updated Jul 21, 2014
One-click install
npx skills add https://github.com/lucidash/dotfiles --skill resolve-qa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: resolve-qa
Source: https://github.com/lucidash/dotfiles/tree/main/claude/skills/resolve-qa
Command: npx skills add https://github.com/lucidash/dotfiles --skill resolve-qa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

이 스킬은 Notion의 QA 이슈 관리 작업을 자동화하여 상황 파악, 브랜치 준비, 이슈 상태 업데이트 및 댓글 작성을 간소화합니다.

Core Features & Use Cases

  • Notion 페이지 조회 및 상태 업데이트
  • Notion 댓글 작성으로 이슈 코멘트 남김
  • LK-ID 또는 Notion URL 입력으로 컨텍스트 파싱 및 워크트리 관리
  • PR 및 브랜치 선택 로직에 따른 빠른 작업 전개

Quick Start

resolve-qa LK-10258 /resolve-qa https://www.notion.so/QA-2fd61056ee1280a4ab14e37ce2261ead 다음에 Notion 상태 업데이트를 실행하려면 같은 인자 다시 실행합니다.

Frequently Asked Questions about resolve-qa

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Notion QA issue updates from the command line?

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.

Can I use a Notion URL to automatically set up a git worktree for bug fixes?

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.

Does this workflow support leaving contextual comments on Notion pages after resolving an issue?

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.

What is the best way to manage QA issue resolution across Notion and git branches?

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.

How do I update a Notion QA page status after preparing a fix branch?

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.

Why do I need to provide an LK-ID or Notion permalink to start the QA automation?

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.