Loading...
Loading...
Found 273 Skills
Review and verify Python code against PEP 8 using flake8, and optionally apply safe formatting fixes with black after explicit user confirmation. Use when users ask to check style compliance, lint Python files, or fix PEP 8 issues in a target folder.
Senior code review pass. Use PROACTIVELY as the FINAL task after code changes. Reviews against project rules, fixes issues, runs quality gates. Focuses on logic and architecture while delegating style to automation.
Issue quality primitives: lint, enrich, decompose. `/issue lint [#N|--all]` — Score issues against org-standards. `/issue enrich [#N]` — Fill gaps with sub-agent research. `/issue decompose [#N]` — Split oversized issues into atomic sub-issues.
Use when reviewing SKILL.md files for structure and trigger quality.
API Design Reviewer
Use when asking about Rust code style or best practices. Keywords: naming, formatting, comment, clippy, rustfmt, lint, code style, best practice, P.NAM, G.FMT, code review, naming convention, variable naming, function naming, type naming, 命名规范, 代码风格, 格式化, 最佳实践, 代码审查, 怎么命名
ESLint JavaScript linter with plugins. Use for code quality.
Run Hadolint to lint Dockerfiles for best practices and security issues. Validates against Docker and ShellCheck rules.
Use this skill when you need to write, update, migrate or fix unit tests.
Use when scaffolding a new Nuxt 4 project with standard config files (prettier, eslint, gitignore, husky, vitest, tsconfig, sops) and bun scripts.
Configure and resolve static analysis warnings to maintain project health.
Use this skill whenever creating or editing any markdown file. Do not wait for an explicit request — if a markdown file is being created or edited, this skill applies.