GitHub
writing-tests
MANDATORY when writing tests. Test behavior, not implementation. Functional tests are primary. Unit tests ONLY for state mutations. Includes fixing flaky tests with condition-based waiting.
☆ 3View skill
Testing & security AI Skills
Discover Testing & security skills, compare source repositories and read the instructions for each workflow.
Categories: Testing & security
Testing & security Clear filters
Browse skills
GitHub
debug
Use when encountering bugs, test failures, or unexpected behavior. Combines systematic debugging framework, root cause tracing, and defense-in-depth validation.
☆ 3View skill
GitHub
show-architecture
Use when exploring/explaining code, designing/updating architecture, or when asked to visualize structure. Shows annotated file trees inline.
☆ 3View skill
GitHub
design
Use when building UI components, styling pages, or making visual/interaction decisions. Guides design thinking, anti-patterns, CSS architecture, and responsive patterns.
☆ 3View skill
GitHub
plan
Use when planning implementation - either writing detailed plans for engineers or structuring complex decisions via questions.
☆ 3View skill
GitHub
pragmatic-engineering
Use when user says KISS, pragmatic, don't overengineer, ship it, keep it simple. Also for planning features, reviewing code, or architectural decisions.
☆ 3View skill
GitHub
verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before as...
☆ 3View skill
GitHub
using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
☆ 3View skill
GitHub
claude-code
Use when working with Claude Code itself - skills, agents, commands, hooks, settings, documentation. Alias "cc". Covers building, testing, sharing skills, updating Claude.md files, and context engineering.
☆ 3View skill
GitHub
codebase-exploration
Use when exploring a codebase to understand structure, find files, check dependencies, or see recent changes. Provides verified commands for effective exploration.
☆ 3View skill
GitHub
reviewing-readability
Code readability review based on "The Art of Readable Code" and Miller's Law (7±2). Triggers: 可読性, 理解しやすい, わかりやすい, 明確, 命名, 変数名, 関数名, ネスト, 深いネスト, 関数設計, コメント, 複雑, 難しい...
☆ 3View skill
GitHub
accessing-google-workspace
gcloud CLI を使用して Google Sheets/Docs にアクセス。 ユーザーが Google Sheets/Docs の URL を共有したとき、または スプレッドシート, Sheets, Docs, Google ドキュメントに言及したときに使用。
☆ 3View skill
GitHub
reviewing-security
OWASP Top 10-based security review and vulnerability detection. Use when reviewing code for security issues, performing vulnerability analysis, or when user mentions security, OWASP, XSS, SQL injection, セキュ...
☆ 3View skill
GitHub
documenting-apis
Generate API specification from codebase - endpoints, types, schemas. Use when generating API documentation, documenting endpoints, or when user mentions API docs, API仕様, OpenAPI, Swagger, REST API, endpoint...
☆ 3View skill
GitHub
reviewing-type-safety
TypeScript type safety patterns and best practices for maximum type coverage. Use when reviewing TypeScript code for type issues, eliminating `any` types, or when user mentions type safety, 型安全, 型カバレッジ...
☆ 3View skill
GitHub
applying-frontend-patterns
Framework-agnostic frontend component design patterns. Use when designing React/Vue/Angular components, applying Container/Presentational pattern, or when user mentions component patterns, フロントエンドパター...
☆ 3View skill
GitHub
analyzing-root-causes
Root cause analysis with 5 Whys methodology. Triggers: root cause, 5 Whys, なぜなぜ分析, 根本原因, 原因分析, symptom fix, 対症療法.
☆ 3View skill
GitHub
applying-code-principles
Fundamental software principles - SOLID, DRY, Occam's Razor, Miller's Law, YAGNI, Readable Code. Use when applying design principles, refactoring code, or when user mentions 原則, シンプル, 複雑, リファクタリン...
☆ 3View skill
GitHub
orchestrating-workflows
Command workflow orchestration patterns for /code, /fix, /audit, and other implementation commands. Triggers: workflow, orchestration, command flow, IDR, test generation, RGRC, quality gates, completion criteri...
☆ 3View skill
GitHub
enhancing-progressively
CSS-first approach - use CSS before JavaScript. Use when implementing layouts, animations, or toggles, or when user mentions レイアウト, スタイル, 位置, アニメーション, 表示/非表示, トグル, レスポンシブ, CSS Gr...
☆ 3View skill
GitHub
reviewing-silent-failures
Silent failure detection patterns for frontend code. Use when reviewing error handling, detecting swallowed errors, or when user mentions silent failure, empty catch, エラーハンドリング, 握りつぶし, swallowed e...
☆ 3View skill
GitHub
formatting-audits
Design document review format with 100-point scoring system for SOW/Spec. Use when reviewing SOW or Spec documents, scoring design quality, or when user mentions SOW review, Spec review, 設計書レビュー, 品質ス...
☆ 3View skill
GitHub
formatting-audits
Design document review format with 100-point scoring system for SOW/Spec. Triggers: SOW review, Spec review, document scoring, 設計書レビュー, 品質スコア.
☆ 3View skill
GitHub
vercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. Use when writing, reviewing, or refactoring React/Next.js code, improving Web Vitals, or when user mentions React performance, Next...
☆ 3View skill
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.