mrlyk
- 28 skills
- 0 followers
- 7 hours ago last updated
- ▌ Learn 2 · mrlykPersist durable learnings from the current session (user corrections, pitfalls and fixes, project decisions not visible in code) into the project knowledge wiki at .superskills/learnings/. Use when the user asks to summarize or persist learnings, or when triggered automatically at session end.
- ▌ Test · mrlykAfter development work is complete, run one full unit-test pass over the changes. Use when wrapping up a coding task ("补测试", "write tests for this", finishing development) — not during development.
- ▌ Clarify · mrlykSurface unresolved decisions in a development request and ask the user before implementing. Use when starting a non-trivial dev task whose requirements leave open questions that would change the implementation (scope, data shape, UX behavior, compatibility), or when the user asks to confirm first ("先确认一下", "有不清楚的先问").
- ▌ Discover · mrlykDiscover an existing project's conventions and generate or refresh minimal AI spec files (.superskills/conventions.md, AGENTS.md, CLAUDE.md). Use when a project lacks AGENTS.md/CLAUDE.md, when the user asks to generate conventions ("生成规范", "init ai docs", "discover conventions"), or when conventions are reported stale.
- ▌ QA · mrlykSingle entry point for all verification. Auto-detects E2E cases and runs e2e-verify internally via CLI.
- ▌ Fix · mrlykFix QA issues from the current implementation revision using TDD, then automatically re-runs authorized QA.
- ▌ Go · mrlykMain entry point for end-to-end feature work. Start a full task with /superharness:go 'requirement', a lite task with /superharness:go [lite] 'requirement', or resume with /superharness:go --task {task-id}.
- ▌ E2e Gen · mrlyk bundleTwo-stage E2E skill: a gate check that decides whether the change has browser-verifiable UI behavior (writes e2e:gate-passed or e2e:skipped trace events, generates nothing), and a generation stage entered only after the user confirms generation. Generates e2e-cases.yaml from prd.md, plan.md, and contract.md, plus e2e-config.yaml on first run.
- ▌ To Coder · mrlyk bundleGenerate a developer-facing efficiency and focus-area report for a completed Superharness task. Use when the user asks to "生成开发者报告", "开发交接报告", "to-coder", "developer report", or when /superharness:to-coder is invoked.
- ▌ To Tester · mrlykGenerate a tester-facing change impact handoff for a completed Superharness task or a standalone current Git change without task artifacts. Use when superharness:finishing-a-development-branch offers the tester handoff, when the user asks to "生成影响范围", "生成测试文档", "生成测试影响范围", or "测试交接文档", or when /superharness:to-tester is invoked.
- ▌ Learn · mrlyk bundlePersist durable project learnings into a topic wiki. Use when the user asks "总结一下经验", "沉淀一下", or "记住这个"; when the user states a convention to persist ("保存为项目规范", "from now on use X"); when the user is correcting an answer or plan; when a verified belief conflicts with the codebase; or when an undocumented project convention surfaces.
- ▌ E2e Verify · mrlyk bundleRun E2E case verification via CLI. Parses cases, starts app, drives agent-browser, produces qa-issues.json + issues/ + process/. Called by QA after tasks pass review.
- ▌ To Prd · mrlykSynthesis only, no interview: solidify an already-resolved requirement discussion into task artifacts (prd.md + task.json + contract.md), self-review, commit, and get user sign-off. Use after batch-grill-me, grill-me, or another discussion has resolved all open questions and the user is ready to write the spec down.
- ▌ Mindmap · mrlyk bundleInfrastructure skill: start a local visualization server that renders Mermaid diagrams in the browser. Write .mmd files with pure Mermaid code, and the browser updates in real-time via WebSocket. Use when the user requests a visualization during requirement discussion or planning.
- ▌ Reopen Task · mrlykReopen a completed Superharness task to fix a post-delivery bug so the fix time keeps accruing to the same requirement. Use when the user reports a bug in work delivered by a completed task ("上次那个功能有 bug", "修一下之前任务的问题", "fix the bug from the last task"), possibly in a fresh session.
- ▌ Grill Me · mrlykInterview engine that grills the user about a requirement, plan, or design through relentless, structured questioning, asking 1-2 focused questions per turn until every branch of the decision tree is resolved. Use directly when the user explicitly asks to be grilled without Wiki lookup.
- ▌ Setup Superharness · mrlyk bundleSet up superharness in a project: scan the codebase to discover conventions and tech stack, write findings into .superharness/spec/, then distill them into AGENTS.md and CLAUDE.md. Use when the user asks to set up superharness, to scan or re-scan the codebase for conventions, or to generate or refresh AGENTS.md / CLAUDE.md.
- ▌ Using Superharness · mrlykSession start guide: explains how to use superharness skills and conventions. Injected by SessionStart hook.
- ▌ Writing Plans · mrlyk bundleUse when you have a spec or requirements for a multi-step task, before touching code. Creates detailed, seam-first implementation plans with vertical TDD steps for superharness workflows.
- ▌ Executing Plans · mrlykUse when an approved implementation plan will be executed inline in a separate session with batch checkpoints
- ▌ Adversarial Review · mrlyk bundleRun an on-demand adversarial review of an already-written PRD or Plan with an available local provider.
- ▌ Batch Grill Me · mrlyk bundleA relentless interview that asks every frontier question at once, round by round. Invoked by superharness:go for new tasks.
- ▌ Systematic Debugging · mrlyk bundleUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes
- ▌ Using Git Worktrees · mrlykUse when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
- ▌ Test Driven Development · mrlyk bundleUse when implementing any feature or bugfix, before writing implementation code
- ▌ Subagent Driven Development · mrlyk bundleUse when executing implementation plans with independent tasks in the current session
- ▌ Finishing A Development Branch · mrlykUse when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
- ▌ Verification Before Completion · mrlykUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always