Loading...
Loading...
Found 818 Skills
Executa refatoração segura e incremental para projetos Go, preservando comportamento e reduzindo complexidade. Use quando o usuário pede para refatorar, simplificar ou melhorar manutenibilidade. Não use para correção de bug (usar bugfix) nem para review/auditoria (usar reviewer).
Review a diff for clarity and safe simplifications, then optionally apply low-risk fixes.
Comprehensive Rust coding guidelines covering ownership, error handling, async patterns, traits, testing, performance, clippy, and documentation. Use when writing new Rust code, reviewing or refactoring existing Rust, implementing async systems with Tokio, designing error hierarchies, choosing between borrowing and cloning, setting up tests or benchmarks, configuring linting, or optimizing performance. Do not use for non-Rust languages or general software architecture unrelated to Rust idioms.
**Mandatory** before any commit or push. Run Definition-of-Done checks from change scope and report exact pass/fail per command.
Phase 2 of the feature workflow — Write code according to the implementation sequence in {slug}-design.md, and submit a completion report in a unified format for user review after finishing. Prerequisites: {slug}-design.md has been approved (standard design includes test design, or fastforward design includes acceptance criteria), and {slug}-checklist.yaml exists in the same directory. Trigger scenarios: User says "The plan is confirmed, start implementation", "Write code according to the plan", "Start working". If you encounter situations not covered by the plan during implementation (new concepts, out-of-scope files, need for patch branches), proactively stop and discuss with the user based on the plan, do not proceed forcefully.
Run OpenAI Codex CLI as an independent reviewer over the current branch, a specific commit, or uncommitted changes. Builds a focused instruction file from the real diff and returns a compact review summary.
Shortcut alias for /superplan. Produce higher-quality code by breaking a feature into small, focused tasks the coding agent can nail one at a time. Works like an engineering team: feature → milestones → ~30-min tasks with specific files, acceptance criteria, and dependencies. Each task runs in a fresh context — narrow scope, full attention, one git commit per task.
Reflect on previus response and output, based on Self-refinement framework for iterative improvement with complexity triage and verification
Used when implementing any feature or fixing bugs, before writing the implementation code
Intelligently analyze code changes and split them into multiple logical commits based on functionality and change types. This skill should be used when users want to commit code changes, especially when there are multiple unrelated changes in the working directory.
Use when receiving code review feedback (especially if unclear or technically questionable), when completing tasks or major features requiring review before proceeding, or before making any completion/success claims. Covers three practices - receiving feedback with technical rigor over performative agreement, requesting reviews via code-reviewer subagent, and verification gates requiring evidence before any status claims. Essential for subagent-driven development, pull requests, and preventing false completion claims.
React/TypeScript 코드 리팩토링을 위한 비판적 분석 및 실행 스킬. 사용자가 컴포넌트 경로와 문제점을 제시하면, 각 문제점을 "수정하기 좋은 코드" 관점에서 비판적으로 검토하고, sequential-thinking으로 단계별 분석 후 리팩토링 계획을 수립하여 실행한다. 트리거: "리팩토링", "개선하고 싶어", "코드 구조 변경", "훅 분리", "응집도", "결합도" 등의 키워드와 함께 React 컴포넌트 경로가 제시될 때 사용.