Loading...
Loading...
Found 30 Skills
Analyzes changed files and improves unit test coverage using project-specific testing conventions from .trellis/spec/ unit-test specs. Determines test scope (unit vs integration vs regression), adds or updates tests following existing patterns, and runs validation. Use when code changes need test coverage, after implementing a feature, after fixing a bug, or when test gaps are identified.
Use when encountering a bug, crash, or test failure. Not for code review or new features.
Review and refactor code in your project according to defined instructions
작업을 마무리하는 스킬. 테스트 확인, 커밋/PR, worktree 정리와 함께 5개의 전문 에이전트로 세션 인사이트를 추출합니다.
Test Case Generator - Based on the theories of Equivalence Partitioning and Boundary Value Analysis, generates high-quality test cases in batches by Test Points (POINT), output in Markdown format. Used when users execute the /testcase-gen command or need to generate test cases.
Smoke test for Alibaba Cloud ALB skill. Validates SDK auth, script compilation, list instances, and health check flows.
Creates test documentation (testing-strategy.md + tests/README.md). Establishes testing philosophy and Story-Level Test Task Pattern. L2 Worker in ln-100-documents-pipeline workflow.
Implements approved specification proposals by working through tasks sequentially with testing and validation. Use when implementing changes, applying proposals, executing spec tasks, or building from approved plans. Triggers include "openspec implement", "implement", "apply change", "execute spec", "work through tasks", "build feature", "start implementation".
Run adversarial browser tests against code changes. Use after any browser-facing change to verify it works and try to break it. Prefer this over raw browser tools (Playwright MCP, chrome tools).
Sub-agent powered code reviews spanning correctness, tests, consistency, and fit
Smoke test for alicloud-skill-creator. Validate repository path conventions, frontmatter quality, script compilation, and README index refresh workflow.
Safe, phase-gated refactoring: CHARACTERIZE with tests, PLAN incremental steps, EXECUTE one change at a time, VALIDATE no regressions. Use when renaming functions/variables, extracting modules, changing signatures, restructuring directories, or consolidating duplicate code. Use for "refactor", "rename", "extract", "restructure", or "migrate pattern". Do NOT use for bug fixes or new feature implementation.