git-commit-convention
Enforces the Bedriftsgrafen project's strict git commit message format and policies.
Enforces the Bedriftsgrafen project's strict git commit message format and policies.
Self-review checklist before marking PR ready - catch clarity, correctness, and maintainability issues with fresh eyes
Comprehensive code documentation standards and guidelines for maintaining up-to-date documentation across Python, HTML, CSS, and JavaScript codebases. Use when creating or modifying code to ensure proper documentation practices and maintainable code.
Write minimal, evergreen code comments that explain complex logic without documenting obvious behavior or temporary changes. Use this skill when adding comments to PHP files, TypeScript/JavaScript files, or any code files, when documenting complex algorithms or business logic, when adding PHPDoc blocks or JSDoc comments, when writing self-documenting code with clear naming, or when reviewing existing comments for relevance and necessity. Focus on keeping code self-explanatory through clear structure and naming rather than relying heavily on comments.
Load when user says "validate docs", "check documentation consistency", "docs vs implementation", or "find documentation mismatches". Systematically compares implementation code against documentation to identify and fix inconsistencies.
Run linters/formatters on changed files and apply safe, mechanical fixes. Use in Flow 3 and Flow 4.
Review code changes following RT Stack conventions and best practices. 按照 RT Stack 规范和最佳实践审查代码变更。 Use when: - Reviewing pull requests - Checking code quality before commit - User mentions "review", "check code", "审查代码", "代码检查"
Run and interpret eo-processor quality gates (Rust+Python) and add the right tests for changes. Use when verifying work, fixing CI failures, or before committing PR-ready changes (fmt/clippy, ruff/mypy, pytest/tox, coverage, and minimal regression tests).
PCE (Process-Context Engine) の出力評価スキル。生成物の品質とLaw(法則)との整合性を検証する。 LDE(Law-Driven Engineering)との統合により、Law遵守チェックも実行。 トリガー条件: - コード生成後(「このコードをレビューして」) - 設計完了後(「設計をチェックして」) - PRマージ前(「マージ前の確認をして」) - 「品質チェックして」 - 「整合性を確認して」 - 「Law遵守をチェックして」
Review production code for bugs, security vulnerabilities, performance issues, and maintainability. Use when reviewing pull requests, code changes, or assessing code quality.
This skill should be used when the user asks for "defensive coding", "input validation", "prevent bugs", "multiple validation layers", or when fixing bugs caused by invalid data reaching deep execution. Validates at every layer.
Verify external libraries, APIs, and frameworks against current documentation before writing code. Use when about to implement features using external dependencies, when writing import statements for third-party libraries, when unsure if a pattern or method is current, or when the user mentions grounding or verification.
Kotlin 코드 작성, 코드 리뷰, 리팩토링 시 사용. 네이밍 규칙, 함수/클래스 설계, 레이어별 책임 분리 등 코딩 컨벤션을 따름.
Implements and enforces code quality gates for TypeScript/React projects. Use when setting up Biome/ESLint/TypeScript, configuring pre-commit hooks (Husky), fixing lint errors, or running quality checks. Examples - "setup code quality", "fix lint errors", "configure Biome", "run quality checks".
Use when writing any code - enforces clean architecture with descriptive names, real implementations, no backward compatibility concerns, and no lint suppressions
Fix ESLint issues in migrated Output SDK code. Use when seeing lint errors after migration, or when writing new Output SDK code that needs to follow project conventions.
Review frontend code for quality, performance, UX, and consistency. Use for .tsx/.ts UI changes or before merges.
Terraformコードのフォーマット、命名規則、およびスタイルの一貫性をチェックします。ユーザーがコードのフォーマット、スタイルのチェック、またはコードの一貫性の確認を求めた場合に使用してください。
AUTOSAR C++14およびCERT C++コーディング規約に準拠したC++14コードレビュー。安全性重視のC++システムのコードレビュー、セキュリティ監査、品質評価、静的解析ツール設定を行う際に使用。
Review code for correctness, maintainability, performance, and security. Produce actionable, prioritized feedback and concrete fixes aligned with repo standards.
Automatically invoked when conducting reviews (code, specs, architecture, UX). Ensures systematic analysis and actionable findings with consistent format.
Rustプロジェクトの型チェック・コンパイルチェック実行スキル。cargo checkによるコンパイルエラー、型エラー検出とレポート。型チェック実行時は必ずエージェント(Task tool)を使用し、直接Bashで型チェックコマンドを実行しない。