Loading...
Loading...
Found 83 Skills
Use this skill for mathematical code verification. Use when reviewing math-heavy code, verifying algorithm correctness, checking numerical stability, aligning with mathematical standards. Do not use when general algorithm review - use architecture-review. DO NOT use when: performance optimization - use parseltongue:python-performance.
Reliable end-to-end engineering workflow for debugging, root-cause analysis, minimal patching, and verification in production codebases. Use when Codex needs to investigate a failure systematically, trace execution, test hypotheses, implement a correct fix, validate the resolution, and check for regressions before declaring the task complete.
Phase-level implementation workflow for builder agents. Handles reading phase files, finding references, invoking domain skills, implementing all steps, and running verification (tests + typecheck). Preloaded into builder agents via skills: field — not user-invocable.
Executes implementation plans with smart task grouping. Groups related tasks to share context, parallelizes across independent subsystems.
Diagnose and fix errors with Codex delegation. Traces error to root cause, researches approach, delegates fix, verifies. Use when: bug reports, error messages, stack traces, test failures.
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.
Verifies that the implementation complies with the specs, design, and task plan. Produces verify-report.md. Trigger: /sdd-verify <change-name>, verify implementation, quality gate, validate change.
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".
Stage 1 spec compliance review. Triggers: /review stage 1. Verifies implementation matches design specification — functional completeness, TDD compliance, and test coverage. Do NOT use for code quality checks — use quality-review instead. Do NOT use for debugging.
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Verify code against paper. Use when user asks "does this match the paper", "check my implementation", or is implementing equations/algorithms from literature.
Test-driven development workflow with philosophy guide - plan → write tests → implement → validate