PANYUXIN6
- 9 skills
- 0 followers
- 7 hours ago last updated
- ▌ Tdd · panyuxin6 bundleExecute test-driven development through coherent red-green-refactor slices. Use when the user explicitly asks for TDD, test-first, red-green-refactor, or a regression test before fixing a bug. Always pair it with testing-guidelines when adding or changing tests; ordinary test requests use testing-guidelines without this skill.
- ▌ Code Review · panyuxin6 bundleReview code and machine-consumed implementation artifacts for defects, risks, quality, correctness, requirements, or standards. Use when the user requests an implementation review, findings, or a review conclusion, including focused reviews. Exclude prose-document review and requests only to read, explain, summarize, map, or trace implementation; neutral verbs such as check or inspect alone do not establish review intent.
- ▌ Brainstorming · panyuxin6 bundleResolve uncertain product or architecture decisions before implementation. Use for explicit brainstorming or design requests, or when unresolved trade-offs, blast radius, or reversal cost could materially change the implementation; clear, local, reversible work proceeds directly.
- ▌ Repo Map First · panyuxin6 bundleLocate code ownership and assess repository-map trust from source evidence. Use for unclear ownership, cross-boundary behavior changes, entry-point or dependency changes, or maps that may mislead placement. Also use for explicit map inspection, use, creation, or repair, and dependent-skill repository-context bootstrap or validation.
- ▌ Simplify Codebase · panyuxin6 bundleFind and, when mutation is explicitly authorized and repository-aware evidence supports it, remove redundant production surface such as dead or superseded code, duplicated state, unused APIs, speculative abstractions, obsolete compatibility paths, dependencies, packages, tests, and documentation. Use for explicit cleanup or simplification requests, or when an already-observed candidate needs structured consumer tracing beyond the current lines. Supports bounded light cleanup and subsystem- or repository-level deep simplification. Do not trigger merely because code review is running, for ordinary lint findings, isolated unused imports, stylistic refactoring, or complexity without consumer evidence.
- ▌ Using Superpowers · panyuxin6Route substantive tasks to the smallest set of explicitly requested or strongly matching skills. Use at task start when skill selection can materially change the process.
- ▌ Testing Guidelines · panyuxin6 bundleDesign, add, modify, or review automated tests and test strategies using risk-driven evidence selection. Use for unit, integration, regression, and end-to-end test work, including as the test-design companion to TDD. Do not use merely to run existing tests or report their results; this skill does not impose test-first sequencing.
- ▌ Reliable Task Execution · panyuxin6 bundleApply lightweight safeguards when task execution involves completion claims, destructive or external-state changes, debugging, long-running or resumable work, subagent delegation, or high-risk review. Use to preserve evidence, recoverability, and user control without imposing a fixed development workflow.
- ▌ Review Design Contracts · panyuxin6 bundleReview a Markdown design document, consume an accepted fix queue, or independently verify accepted fixes with layered contract extraction, architecture reasoning, adversarial falsification, deterministic evidence gates, risk-based partial re-review, and human-only admission. Use only when the user explicitly invokes $review-design-contracts with a repository design-document path, asks to apply one of its queued fix runs, or asks to verify fixes from one of its queued review runs. Use the sibling repo-map-first skill to bootstrap missing repository context or validate relevant context that may be stale before review.