Menu
SkillsMP has collected 11 skills from oopsla5xx/oops-skills. Open a skill to review its source and details.
Showing 11 of 11 collected skills.
Review PR diff against the spec before shipping โ check spec compliance, conventions, scope, required security checklist, and test coverage. Outputs a structured verdict (APPROVE / REQUEST CHANGES / COMMENT). Run after self-check, before Phase 4 ship.
Systematic bug investigation workflow. Tool-agnostic but MCP-aware โ test cases and MCP tools are evidence sources, not prerequisites. Applies to any stack (frontend, backend, CLI, mobile, distributed systems).
Decide whether to ask before coding or proceed with stated assumptions. Small/clear tasks โ do it. Large/ambiguous tasks โ state assumptions and ask at most 1 critical question. Run at the start of any task.
Generate a pull request description by filling in the .github/PULL_REQUEST_TEMPLATE.md from spec, git diff, and commit history. Outputs ready-to-use text or creates PR via gh CLI. Run as part of Phase 4 ship.
Implement each step from the plan using TDD โ write failing test first, then minimal code to pass, then refactor. Run for each unchecked step in the Plan section of .ai/tasks/<name>.md.
Break a spec file into ordered, concrete implementation steps with done criteria. Appends a Plan section to the existing .ai/tasks/<name>.md. Run after write-spec, before coding.
Bootstrap .ai/ context files โ auto-detect stack and fill commands.md, architecture.md, conventions.md instead of filling TODO placeholders manually. Run when setting up oops-skills template in a new project.
Final ship step โ push branch, open PR on GitHub, update status.md, clean up task files. Run after review-pr APPROVE and create-pr-description.
Refresh stale .ai/ context files before starting a task โ detect which of commands.md, architecture.md, conventions.md are outdated and patch only those sections. Run at the start of each task session.
Convert clarify-scope discussion into a structured spec file at .ai/tasks/<name>.md. Run after clarify-scope resolves assumptions and scope. Captures decisions before they're lost in conversation history.
Generate manual test scenarios (UC/TC) from the spec file after implementation โ use cases and step-by-step test cases for human testers to verify the feature by hand. Output saved to .ai/tasks/<name>-manual-tests.md.