fix-markdown-lint
Fix markdown linting errors in documentation files
Fix markdown linting errors in documentation files
Enforce high-quality Rust coding standards including toolchain usage, core semantics, API design, and linting rules. This skill should be used when writing, reviewing, or refactoring Rust code to ensure it meets production-grade quality.
Run analyzer MCP tools (Ruff + optional dead-code scan) as a quality gate before QA/UAT/release.
Enforce Clean Architecture with strict dependency direction, domain/application/adapter/infrastructure layering, and file/function size limits when the user asks to build a feature, refactor a module, add a full-stack capability, or improve architecture quality. Require a proposed `tree` structure before coding and include a self-review that checks for architectural leaks, boundary violations, and limit compliance after code is produced.
Runme.dev形式の実行可能マークダウン作成・編集用規約。 使用タイミング: (1) マークダウンファイルに実行可能なコードブロックを追加(verify.md, README.mdなど) (2) Runme.devセル設定の追加・編集(name, cwd, excludeFromRunAllなど) (3) runme fmtでフォーマット適用 (4) 既存Runmeファイルの修正・改善
全面代码审查,检查安全漏洞、代码质量和最佳实践。 使用场景: - "code review" / "代码审查" / "审查代码" / "review 一下" - "检查代码质量" / "代码有什么问题" - "安全审查" / "找漏洞"
Validate and lint structured data files (YAML, JSON, TOML) for consistency, required fields, syntax errors, and schema compliance.
WordPress theme and plugin README auditor that verifies accuracy, removes exaggerated claims, and ensures maintainability. Use when reviewing or updating README files for WordPress projects (themes, child themes, plugins) to ensure all claims are verifiable against the actual codebase and that documentation remains accurate over time.
Run all quality checks including linting, formatting, and type checking. Use when user asks to check code quality, run checks, or verify code before committing.
コードレビューを実施するスキル(SDD仕様書整合性・コーディング規約・セキュリティ・テスト品質)
Analyze and reduce cognitive load in code by identifying complex conditionals, deep nesting, shallow modules, excessive abstractions, and architectural over-engineering. Use when reviewing code quality, refactoring for maintainability, or simplifying systems. Keywords: cognitive load, complexity, refactor, simplify, maintainability, readability, mental overhead, abstraction, architecture review
Performs comprehensive code review analyzing bugs, security issues, best practices, performance, and suggesting improvements
Pre-review preparation with formatted diffs and clear PR descriptions
Python stack configuration - uv, ruff, mypy, pytest with 96% coverage threshold
Static analysis issue detection patterns and rules
Complete code quality workflow with ESLint, Prettier, TypeScript, Husky hooks, and type safety standards. Run before every commit/push.
dotnet format, prettier 및 기타 포맷팅 도구를 사용하여 코드를 정리합니다. 코드 스타일 수정, 포맷 일관성 유지 또는 커밋 전 코드 준비가 필요한 작업에서 사용합니다.
コード品質チェックと改善提案。Lintエラー修正、未使用コード削除、リファクタリング時に使用。警告、unused、refactor時に使用。
Review JusticeHub code against ACT ecosystem values. Enforces cultural protocols, ALMA principles, and regenerative design.
Code review with project-specific conventions for Xbox 360 portfolio site. Use when reviewing code, checking PRs, auditing files, or when user mentions "review", "check code", "audit", "PR review", "code quality", or "best practices".
Infer and verify install/test/lint/build commands for the repo.
Validates workflow YAML files to ensure structure and schema correctness.
Ensures code follows quality standards. Apply when reviewing or writing production code.