Loading...
Loading...
Found 54 Skills
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
Run Rust tests after making changes to verify correctness
Write Rust tests to verify correctness of Rust code.
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.
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.
Verify completed implementation against the plan. Checks that all tasks were fully implemented, nothing was forgotten, code compiles, tests pass, and quality standards are met. Use after "/aif-implement" completes, or when user says "verify", "check work", "did we miss anything".
Improve test coverage in the OpenAI Agents Python repository: run `make coverage`, inspect coverage artifacts, identify low-coverage files, propose high-impact tests, and confirm with the user before writing tests.
Intelligently upgrade npm dependencies with breaking change research for major version updates. Use when the user asks to "update dependencies", "upgrade npm packages", "check for updates", or "update npm deps".
Run quality gates on implemented feature: tests, lint, type checks, and custom validation. Use after /feature-implement completes. Use for "validate feature", "run quality gates", "check feature", or "/feature-validate". Do NOT use for ad-hoc linting or debugging.
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".
Read-only drift detector. Diffs SPEC.md against current code and reports violations grouped by severity. Writes nothing — suggests remedies via the spec or build skills but never invokes them. Triggers when the user asks to check drift, audit the spec, verify invariants, or ask whether code still matches the spec. Phrasings: "check drift", "audit the spec", "does the code still match §V", "check invariants", "spec vs code".