ワンクリックでManusで任意のスキルを実行

revealui-debugging

スター6

フォーク0

更新日2026年7月16日 20:27

Systematic debugging workflow for RevealUI. Use when encountering any bug, test failure, unexpected behavior, error, or broken functionality. Prevents shotgun debugging.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

RevealUIStudio

RevealUIStudio/revealui

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

RevealUI Debugging Workflow

When something breaks, follow this process. Do not skip steps.

The Process

1. Reproduce

Get the exact error message, stack trace, or unexpected output
Find the minimal reproduction case
Confirm it reproduces consistently (not flaky)
If it only fails under turbo run test, see $revealui-testing for concurrency triage

2. Hypothesize

Form ONE specific hypothesis about the root cause
Write it down before changing any code
Base it on evidence (error message, stack trace, git blame), not intuition

3. Validate

Design a test or check that confirms/refutes your hypothesis
Run it
If refuted, form a new hypothesis — do not stack unrelated fixes

4. Fix Narrowly

Change the minimum code to fix the root cause
Do not refactor surrounding code
Do not fix adjacent issues you noticed along the way (file them separately)

5. Verify

Run the original failing test/scenario
Run pnpm --filter <package> test to check for regressions
Run npx biome check --write <file> on changed files

6. Commit

One commit for the fix
Format: fix(scope): description of what was broken

Anti-Patterns

Changing multiple things at once ("shotgun debugging")
Fixing symptoms instead of root causes
Adding try/catch blocks to silence errors
Increasing timeouts to hide race conditions
Reverting to "known good" without understanding what broke
Asking "does this fix it?" without a hypothesis

Common RevealUI Debugging Paths

Symptom	First Check
Import error	Package built? `pnpm --filter <pkg> build`
Type error across packages	`pnpm typecheck:all` — check `workspace:*` versions
Test passes alone, fails in gate	Concurrency pressure — see `$revealui-testing`
DB/vector query error in unexpected path	Check you use the single `@revealui/db` Drizzle client — see `$revealui-db`
Biome error after edit	Run `npx biome check --write <file>`

このリポジトリの他の Skills

同じリポジトリ

revealui-conventions

RevealUIStudio/revealui

RevealUI coding conventions for any code task — writing, editing, reviewing, creating, fixing, refactoring, changing, adding, or updating TypeScript, React, CSS, or config files. Covers TypeScript strict mode, ES Modules, Biome formatting, Tailwind v4 syntax, conventional commits, monorepo workspace protocol, feature gating, parameterization, and unused declaration policy.

2026-07-166

revealui-db

RevealUIStudio/revealui

RevealUI database conventions for any task involving database, schema, query, migration, Drizzle ORM, Neon, PostgreSQL, pgvector, vectors, embeddings, or data modeling. Covers the single Neon-primary database and its pgvector tables.

2026-07-166

revealui-deploy

RevealUIStudio/revealui

RevealUI deployment guide — Vercel configuration, GitHub Actions deploy workflow, secret management, domain aliasing, and troubleshooting. Invoke when working on deploy.yml, vercel.json, deployment secrets, domain configuration, or debugging deploy failures.

2026-07-166

revealui-review

RevealUIStudio/revealui

Code review checklist for RevealUI. Use when reviewing code, completing a feature, checking quality, or before committing. Invoke explicitly with $revealui-review.

2026-07-166

revealui-safety

RevealUIStudio/revealui

RevealUI safety guardrails for any code task — editing, writing, creating, fixing, refactoring, changing, adding, updating, or removing files. Protects credentials, enforces import boundaries, ensures code quality, and verifies work before completion.

2026-07-166

revealui-tdd

RevealUIStudio/revealui

Test-driven development workflow for RevealUI. Use when implementing any feature, fixing bugs, adding functionality, or writing new code. Enforces write-test-first, red-green-refactor cycle. Works with Vitest and React Testing Library.

2026-07-166

RevealUI Debugging Workflow

When something breaks, follow this process. Do not skip steps.

The Process

1. Reproduce

Get the exact error message, stack trace, or unexpected output

Find the minimal reproduction case

Confirm it reproduces consistently (not flaky)

If it only fails under turbo run test, see $revealui-testing for concurrency triage

2. Hypothesize

Form ONE specific hypothesis about the root cause

Write it down before changing any code

Base it on evidence (error message, stack trace, git blame), not intuition

3. Validate

Design a test or check that confirms/refutes your hypothesis

Run it

If refuted, form a new hypothesis — do not stack unrelated fixes

4. Fix Narrowly

Change the minimum code to fix the root cause

Do not refactor surrounding code

Do not fix adjacent issues you noticed along the way (file them separately)

5. Verify

Run the original failing test/scenario

Run pnpm --filter <package> test to check for regressions

Run npx biome check --write <file> on changed files

6. Commit

One commit for the fix

Format: fix(scope): description of what was broken

Anti-Patterns

Changing multiple things at once ("shotgun debugging")

Fixing symptoms instead of root causes

Adding try/catch blocks to silence errors

Increasing timeouts to hide race conditions

Reverting to "known good" without understanding what broke

Asking "does this fix it?" without a hypothesis

Common RevealUI Debugging Paths

Symptom

First Check

Import error

Package built? pnpm --filter <pkg> build

Type error across packages

pnpm typecheck:all — check workspace:* versions

Test passes alone, fails in gate

Concurrency pressure — see $revealui-testing

DB/vector query error in unexpected path

Check you use the single @revealui/db Drizzle client — see $revealui-db

Biome error after edit

Run npx biome check --write <file>

name	revealui-debugging
description	Systematic debugging workflow for RevealUI. Use when encountering any bug, test failure, unexpected behavior, error, or broken functionality. Prevents shotgun debugging.