Loading...
Loading...
Found 29 Skills
Use when encountering a bug, crash, or test failure. Not for code review or new features.
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.
작업을 마무리하는 스킬. 테스트 확인, 커밋/PR, worktree 정리와 함께 5개의 전문 에이전트로 세션 인사이트를 추출합니다.
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".
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.
Review and refactor code in your project according to defined instructions
Before declaring work complete, checks for loose ends: unused imports, TODO comments created, missing tests, stale references, incomplete error handling. Activates after implementing features or fixes. The cleanup that always gets skipped.
Build health audit worker (L3). Checks compiler/linter errors, deprecation warnings, type errors, failed tests, build configuration issues. Returns findings with severity (Critical/High/Medium/Low), location, effort, and recommendations.
Minimal smoke test for SLS log query skill. Validate SDK auth and one bounded query.
Smoke test for alicloud-network-cdn. Validate minimal authentication, API reachability, and one read-only query path.
Smoke test for alicloud-compute-swas-open. Validate minimal authentication, API reachability, and one read-only query path.
Execute coding tasks with a strict delivery workflow: build a full plan, implement one step at a time, run tests continuously, and commit by default after each step (`per_step`). Support explicit commit policy overrides (`final_only`, `milestone`) and optional BDD (Given/When/Then) when users ask for behavior-driven delivery or requirements are unclear.