Loading...
Loading...
Found 174 Skills
Use when running a scheduled mechanical maintenance pass over a repo — dead code removal, useless-test pruning, layering-violation fixes, duplicate unification, logic bugfixing, logic simplification, or excess-abstraction flattening. Invoked as `/cadence:maintenance-routine <archetype>`, typically from a scheduler (cron, a CI schedule, or an agent workbench's time trigger). One archetype per invocation; opens PRs and never merges. NOT for reviewing a PR (use pr-review), NOT for ad-hoc refactoring the user asked for directly.
Turn a process that lives in the owner's head into a written SOP their staff can actually follow: one guided sitting ending in a markdown note with a step-by-step RACI table and a swimlane map filed beside it. Works with or without a second-brain vault. Use when the user wants a process documented as an SOP ("write an SOP", "document this process", "SOP for <anything>", "帮我写 SOP", "把流程变成 SOP"), and when they resume a draft left mid-sitting ("continue the SOP", "接着上次那个 SOP"). NOT for setting up a second brain, building a vault, capturing a business into rooms, weekly maintenance, or giving an AI a persona: those belong to the my-second-brain skill, which is installed and updated separately from this one.
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation frameworks; analyzing coverage gaps; performance testing with k6 or Artillery; security testing with OWASP methods; debugging flaky tests; or working on QA, regression, test automation, quality gates, shift-left testing, or test maintenance.
Use when running an infra-only health audit across Pylot systems — LaunchAgent, cron, secrets, labels, branches, and issues.
Schedule tasks with safety; use withoutOverlapping, onOneServer, and visibility settings for reliable cron execution
Perform a structured maintainer-style PR review for the mariadb-operator repository. Gathers PR context, triages the change, and evaluates correctness, safety, pitfalls, backwards compatibility and code quality against the project conventions documented in AGENTS.md. Use whenever the user mentions a mariadb-operator PR number or URL and wants any kind of judgment on it — "review this PR", "what do you think of #1234", "is this safe to merge", "assess this diff", "take a look at this change" — even if they don't literally say "review".