Loading...
Loading...
Found 80 Skills
Run /check-onboarding, then fix the highest priority onboarding issue. Creates one fix per invocation. Invoke again for next issue. Use /log-onboarding-issues to create issues without fixing.
Dispatch implementation tasks to agent teammates in git worktrees. Triggers: 'delegate', 'dispatch tasks', 'assign work', or /delegate. Spawns teammates, creates worktrees, monitors progress. Supports --fixes flag. Do NOT use for single-file changes or polish-track refactors.
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".
Check Next.js compilation errors via a running dev server. Turbopack only. MANDATORY after every code edit before reporting work complete. Replaces `next build`.
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.
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.
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.