Loading...
Loading...
Found 111 Skills
Attack a code change and report what survives. Dispatches independent reviewers in parallel, each with a single job and no access to the implementer's reasoning: one hunts correctness bugs blind to the issue, one hunts requirement gaps against the issue text, one runs outside the process entirely. Optionally re-attacks its own findings, then synthesizes what is left. Returns findings and changes nothing — no tooling, no autofix, no edits. On request it publishes to the author, gated on demonstrated evidence. Every phase is configurable.
Validate that implementation matches specs, design, and tasks. Trigger: When the orchestrator launches you to verify a completed (or partially completed) change.
Use when you have a written implementation plan to execute with review checkpoints
Team-orchestrated implement → verify → fix → archive cycle
This skill should be used when the user asks to "verify code", "run verification", "check quality", "validate changes", or before creating a PR. Provides comprehensive verification including build, type check, lint, tests, security scan, and diff review.
Phase 3 of the feature workflow – Complete the acceptance closed loop. Two tasks: First, check layer by layer against {slug}-design.md to verify if the implementation deviates from the plan; if deviations are found, fix them immediately instead of just "noting them down" in the report. Second, integrate this feature into the project's overall architecture documentation. Finally, produce a {slug}-acceptance.md as the closed-loop proof for the entire workflow. Predecessor dependency easysdd-feature-implement must be completed. Trigger scenarios: User says "The feature is done, let's accept it", "Do the final check", "Prepare for merge", "Generate the acceptance report".
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Use before changing a repository that has adopted this skill, or when the user asks for it. Ticket, gwt worktree, verify, PR, merge, clean up. Skip read-only tasks.
Documentation knowledge correctness validation. Inspect whether the technical descriptions in OpenHarmony API documentation are consistent with authoritative standards and specifications (W3C, CSS, etc.), mathematical definitions, or industry facts. When a knowledge issue is found, further compare it against the implementation code to distinguish a "documentation error," a "code implementation error," or an inconsistency across all three. Trigger phrases: documentation description validation, documentation knowledge correctness, whether a description is accurate, parameter description validation, documentation correction, and documentation-to-code comparison.
Check Next.js compilation errors via a running dev server. Turbopack only. MANDATORY after every code edit before reporting work complete. Replaces `next build`.
Create a behavior-driven Markdown implementation plan for a feature or bug fix, with scenarios linked to tasks and post-implementation code verification.
Implement an agreed change from findings, a spec, tickets or a concrete request; verify the result, prepare a draft PR and update authorized working records. Use when implementation is authorized, not for discovery or assessment alone.