minghinmatthewlam
- 12 skills
- 0 followers
- 7 hours ago last updated
- ▌ Verify · minghinmatthewlam bundleVerify code changes in this repo on the right real surface. Use when the user asks to verify, test, self-test, prove something works, or when implementation is complete and verification is still needed. For `apps/desktop`, choose the correct Electron Playwright lane (`core`, `live`, or `native`), use the shared desktop helpers, rerun the owning lane for `core` and `live`, and use the targeted native spec by default for `native`.
- ▌ Testing Windows Desktop · minghinmatthewlamEnd-to-end test the pi-gui Electron desktop app on Windows. Use when verifying Windows compatibility (dev launcher, PATH, folder picker, integrated terminal / node-pty) or any apps/desktop change on Windows.
- ▌ New Task · minghinmatthewlamClarify a new task by stating the goal the agent believes the user wants, showing its current understanding, and asking only product-related or high-priority questions that could materially change the outcome. Use before planning or implementation when the task needs alignment.
- ▌ Concisely · minghinmatthewlam bundlePresent concise plans, progress updates, findings, and final reports that keep the human oriented, informed, and able to learn how the project works. Use for complex agent coding work and focus on the most important points and decisions.
- ▌ Find Bugs · minghinmatthewlam bundleFind important, high-confidence correctness bugs and edge cases in an existing codebase. Use when the user asks to inspect a repository, subsystem, or implementation for bugs, failure modes, incorrect behavior, or overlooked edge cases.
- ▌ Autoreview · minghinmatthewlam bundleRun the bundled OpenClaw structured code-review helper for local changes, branches, commits, and PRs. Use for ordinary code-review requests, default closeout review, or an explicitly requested Codex/Claude review panel.
- ▌ Repo Setup · minghinmatthewlamSet up or refactor a repository so agents naturally follow its intended architecture and important mistakes fail mechanically. Use when the user invokes $repo-setup, asks to make a repo agent-friendly, or wants important repository rules enforced through structure, types, tooling, tests, or CI.
- ▌ Skills Audit · minghinmatthewlam bundleAudit agent skills for triggering quality, correctness, context efficiency, redundancy, structure, failure guidance, and coverage gaps. Use when the user asks to review, improve, compare, simplify, or evaluate skills in global, repo-local, Claude, Codex, or custom skill paths.
- ▌ Explain Report · minghinmatthewlam bundleCreate a self-contained HTML explanation when the user requests one or when important, durable project knowledge is materially easier to understand visually than in concise chat. Use for significant architecture, research, decisions, incidents, audits, or changes that the user may revisit. Do not use for routine status, simple answers, or unverified findings.
- ▌ Learn From Mistake · minghinmatthewlam bundleFind why an agent produced a bad result, strengthen the code, repository, verification, tooling, or workflow that enabled it, then retry the original task. Use when the user asks to learn from a mistake, prevent recurrence, or postmortem an agent failure.
- ▌ Create Verification Skill · minghinmatthewlam bundleGenerate a project-local verification skill that drives your app the way a user does — any language, framework, or platform. Use for $create-verification-skill, "make a control skill for this repo", or when a project has no scripted way to prove UI/CLI/service behavior.
- ▌ Maintain Verification Skill · minghinmatthewlam bundlePeriodic pass that keeps a project's verification skill and feature map honest: parallel source readers per feature, one live session driving every feature, at most one PR of proven corrections. Use for $maintain-verification-skill or "audit the verify skill".