一键导入
这个仓库中的 skills
[Workflow] Explore an idea and design a solution before implementing
Use when the what or how of a change has open questions requiring collaborative design dialogue with the user — before committing to an approach
[Agent] Subagent persona for reviewing code changes against a plan and quality standards
Use when approaching complex exploration, research, or synthesis tasks — understanding systems, codebases, domains, or architectures before proposing changes or designs
Use when facing 2+ tasks that can proceed without shared state, sequential dependencies, or mutual file edits
[Workflow] Execute an implementation plan task by task with review checkpoints
Use when you have a written implementation plan to execute — before touching code on any multi-step planned work
Use when implementation is complete and you need to decide how to integrate, preserve, or discard the work on a development branch
Use when setting up a new OCA harness from scratch, resolving OCA-specific issues (model prefix, variant config paths), or comparing harness capabilities — not for adding rules/skills/MCP to an existing harness (use agent-configuration for that)
Use when writing or debugging ocibuild.conf, troubleshooting build failures on OCI Build Service runners, or publishing artifacts to Artifactory generic repos.
[Workflow] Prepare a code change for review — test, lint, commit, PR, issue tracker
Use when receiving code review feedback — before implementing suggestions, especially when feedback is ambiguous, technically questionable, or spans multiple items requiring prioritization
Use when a feature, fix, or task is complete and ready for external eyes — or when stuck and a fresh perspective would unblock progress
Use when executing an implementation plan with multiple independent tasks that benefit from fresh context per task
Use when encountering any bug, test failure, unexpected behavior, or system anomaly — before proposing fixes
Use when facing complex, multi-step work that needs to be broken into implementable tasks before starting — especially when the scope feels large or uncertain
Use when implementing any feature, bug fix, or behavior change — before writing production code
[Workflow] Create a detailed implementation plan from a spec or requirements
Use when you have requirements or a spec for multi-step work and need a concrete implementation plan before touching code