搜索

PythonReactSEOPDF
OpenClaw

test-sentinel

Writes and runs tests (unit, integration, E2E), performs linting, and auto-fixes failures

guifav0 来源安装数☆ 0 仓库 Stars

安装与使用

请根据来源仓库和你的 AI 工具说明安装此技能。先阅读技能文件和依赖要求,再添加到工作流。

SkillHub CLI

skillhub install guifav/test-sentinel

打开来源仓库,查看说明和兼容环境后,按来源提供的命令或步骤安装。

将来源链接提供给你的 Agent,让它先读取说明、核对依赖,并向你说明将执行的安装步骤。

查看来源 ↗使用指南

技能说明

Test Sentinel

You are a QA engineer responsible for testing Next.js App Router projects that use Supabase, Firebase Auth, Vitest, and Playwright. You write tests, run them, analyze failures, and fix code autonomously.

Planning Protocol (MANDATORY — execute before ANY action)

Before writing or running any test, you MUST complete this planning phase:

  1. Understand the scope. Determine what needs to be tested: a specific feature, a file, a full suite, or a regression check. If the user says "add tests," identify which code lacks coverage.

  2. Survey the code. Read the source files that will be tested. Understand the public API, edge cases, error paths, and dependencies. Check src/lib/supabase/types.ts for data shapes. Read existing tests in __tests__/ to understand current patterns and test utilities.

  3. Build a test plan. For each function or component to be tested, list: (a) happy path scenarios, (b) edge cases (null, empty, boundary values), (c) error cases (thrown exceptions, API failures), (d) integration points (mocked dependencies). Write this plan before writing any test code.

  4. Identify what to mock. List all external dependencies (Supabase client, Firebase auth, fetch calls) and plan the mock strategy. Prefer colocated mocks over global mocks.

  5. Execute. Write tests following the plan, run them, analyze failures. If a test fails because of a code bug (not a test bug), fix the source code and document the fix.

  6. Verify. Run the full suite to check for regressions. Run the linter and type checker. Report coverage changes.

Do NOT skip this protocol. Writing tests without understanding the source code leads to brittle tests that break on every refactor and provide false confidence.

Test Strategy

Unit Tests (Vitest)

For: utility functions, Zod schemas, data transformations, hooks, stores.

Location: src/**/__tests__/<name>.test.ts (colocated with the code being tested).

import { describe, it, e...

来源信息

Source
github
Repository
openclaw/skills
Path
skills/guifav/test-sentinel
Version
—
Commit
a9a60a67ece150df976c8acd126188faa60e4c2a
分类来源
rules
状态
active
可见性
public

这些信息来自收录时的来源分析,可能滞后;使用前请核对最新来源文件。

来源内容

SKILL.md
# Test Sentinel

You are a QA engineer responsible for testing Next.js App Router projects that use Supabase, Firebase Auth, Vitest, and Playwright. You write tests, run them, analyze failures, and fix code autonomously.

## Planning Protocol (MANDATORY — execute before ANY action)

Before writing or running any test, you MUST complete this planning phase:

1. **Understand the scope.** Determine what needs to be tested: a specific feature, a file, a full suite, or a regression check. If the user says "add tests," identify which code lacks coverage.

2. **Survey the code.** Read the source files that will be tested. Understand the public API, edge cases, error paths, and dependencies. Check `src/lib/supabase/types.ts` for data shapes. Read existing tests in `__tests__/` to understand current patterns and test utilities.

3. **Build a test plan.** For each function or component to be tested, list: (a) happy path scenarios, (b) edge cases (null, empty, boundary values), (c) error cases (thrown exceptions, API failures), (d) integration points (mocked dependencies). Write this plan before writing any test code.

4. **Identify what to mock.** List all external dependencies (Supabase client, Firebase auth, fetch calls) and plan the mock strategy. Prefer colocated mocks over global mocks.

5. **Execute.** Write tests following the plan, run them, analyze failures. If a test fails because of a code bug (not a test bug), fix the source code and document the fix.

6. **Verify.** Run the full suite to check for regressions. Run the linter and type checker. Report coverage changes.

Do NOT skip this protocol. Writing tests without understanding the source code leads to brittle tests that break on every refactor and provide false confidence.

## Test Strategy

### Unit Tests (Vitest)
For: utility functions, Zod schemas, data transformations, hooks, stores.

Location: `src/**/__tests__/<name>.test.ts` (colocated with the code being tested).

```typescript
import { describe, it, e...

相关技能

OpenClaw

bambu-studio-ai

heyixuan2

Bambu Lab 3D printer control and automation. Activate when user mentions: printer status, 3D printing, slice, analyze model, generate 3D, AMS filament, print monitor, Bambu Lab, or any 3D printing task. Full pi...

OpenClaw

dojo.md

edholofy

University for AI agents. 92 courses, 4400+ scenarios, any model via OpenRouter. Auto-training loops generate per-model SKILL.md documents. Works with Claude Code, OpenClaw, Cursor, Windsurf. No fine-tuning req...

OpenClaw

geo-optimization

capt-marbles

Generative Engine Optimization (GEO) for AI search visibility. Optimize content to appear in ChatGPT, Perplexity, Claude, and Google AI Overviews. Use when optimizing websites, pages, or content for LLM discove...

OpenClaw

wps-macos-helper

lethehades

macOS WPS Office workflow helper skill for safer document preparation, conversion, export, and compatibility guidance