Skills matching the name, description or GitHub author.
Provides AI consultation workflows, prompt templates, and best practices for multi-model consultation. Use when user asks for "second opinion", "ask codex", "ask gemini", "AI code review", "external AI consulta...
Reviews code changes before merging. Use when reviewing PRs, checking staged changes, reviewing diffs, code review, merge readiness check, or validating changes before commit/push.
SECIモデル（野中郁次郎）に基づく組織知識の形式知化と共有を専門とするスキル。 暗黙知（経験、勘、ノウハウ）を形式知（ドキュメント、パターン）に変換し、体系化することで組織全体で再利用可能な知識として活用する。 A...
Senior engineer code review for PRs, diffs, and code snippets focusing on security vulnerabilities, OWASP compliance, performance bottlenecks, maintainability, error handling, and architectural patterns
PolicyEngine code review patterns - validation checklist, common issues, review standards
C# code style and naming conventions based on POCU standards. Covers naming rules (mPascalCase for private, bBoolean prefix, EEnum prefix), code organization, C# 9.0 patterns. Use PROACTIVELY for C# code review...
Google Gemini CLI fundamentals for code analysis, review, and validation. Use when (1) executing gemini commands for code review/analysis, (2) configuring models (gemini-3-flash-preview (default)/gemini-3-pro-p...
OpenAI Codex CLI fundamentals for code analysis, review, and validation. Use when (1) executing codex commands for code review/analysis, (2) configuring models (gpt-5.2-codex/gpt-5.2/gpt-5.1-codex-max/codex-min...
Use before code review - determine if change is minor (review new code only) or major (review impacted code too)
Use after code review - implement ALL findings; any finding not fixed MUST have tracking issue created; no finding disappears without trace
Use after implementing features - 7-criteria code review with MANDATORY artifact posting to GitHub issue; blocks PR creation until complete
Use for any development work - the master 13-step coding process that orchestrates all other skills, ensuring GitHub issue tracking, proper branching, TDD, code review, and CI verification
Systematic quality verification procedures for code review and delivery. Use when validating completed work, conducting code reviews, or ensuring production readiness.
Use for any development work - the master 13-step coding process that orchestrates all other skills, ensuring GitHub issue tracking, proper branching, TDD, code review, and CI verification
Use after implementing features - 7-criteria code review with MANDATORY artifact posting to GitHub issue; blocks PR creation until complete
Use after code review - implement ALL findings; any finding not fixed MUST have tracking issue created; no finding disappears without trace
Use before code review - determine if change is minor (review new code only) or major (review impacted code too)
Library of battle-tested security prompt templates for secure feature implementation. Use when implementing forms, endpoints, authentication, authorization, file uploads, or conducting security reviews. Trigger...
Security analysis and threat modeling prompt templates for STRIDE analysis, code review, OWASP compliance, and vulnerability assessment. Use for security planning, pre-deployment reviews, and ongoing threat ass...
Guide for conducting thorough code reviews focusing on correctness, security, performance, maintainability, and best practices
Process and implement code review feedback systematically. Use when user provides reviewer comments, PR feedback, code review notes, or asks to implement suggestions from reviews. Activates on phrases like "imp...
Enforces TypeScript best practices when writing code. Automatically enables strict typing for TypeScript projects, prevents `any` usage, and recommends generic constraints. Activate on TS/TSX files, new feature...
Manufacturing-fokussierter Continuous Improvement Skill fuer fabrikIQ. Implementiert Lean Manufacturing Prinzipien (5 Whys, Ishikawa, PDCA) fuer systematische Problemloesung und Qualitaetsverbesserung. Aktivier...
Perform comprehensive C#/.NET code reviews focusing on clean code, security, testing, performance, and documentation
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.