GitHub
quality-gate
Strict validator. Runs format, lint, types, and build checks via script.
Skills IA blockchain code quality
Découvrez les skills blockchain code quality, comparez leurs dépôts et consultez leurs instructions.
Catégories: blockchain code quality
blockchain code quality Effacer les filtres
Explorer
GitHub
feedback-loop
Update CLAUDE.md or rules when patterns of errors emerge
GitHub
code-stats
Analyze codebase statistics with tokei (line counts by language) and difft (semantic AST-aware diffs). Use for project composition, refactoring scope, codebase metrics.
GitHub
rsls-fix
Fix errors caused by corrupted rsls* files. Use when any operation fails mentioning rsls* files (e.g., "bad object *.rslsc", "missing *.rslsd", file not found *.rsls*).
GitHub
python-conventions
Python tooling conventions for this organization. Use when working with Python projects, fixing linting issues, or managing dependencies.
GitHub
run-linters
Run linters after code changes to verify code quality. Use this skill after completing code modifications to catch and fix any linting issues.
GitHub
testing-patterns
Testing strategies, patterns, and best practices across test types. Auto-triggers when writing tests, setting up test infrastructure, or improving test coverage.
GitHub
post-review
Review and lightly edit a single blog post under _posts/ for prose quality and source hygiene, without changing code examples or post structure.
GitHub
code-review
Perform comprehensive code reviews with actionable feedback. Use when reviewing pull requests, checking code quality, analyzing changes, or when the user mentions "review", "PR", "pull request", "check code", "...
GitHub
code-review
Perform comprehensive code reviews with actionable feedback. Use when reviewing pull requests, checking code quality, analyzing changes, or when the user mentions "review", "PR", "pull request", "check code", "...
GitHub
testing-anti-patterns
This skill should be used when reviewing test code, the user asks "is this test good", "test quality", "mock properly", or when tests behave unexpectedly. Identifies common testing mistakes.
GitHub
google-shell-style-guide
This skill should be used when the user asks to "refactor shell script", "fix bash style", "review shell code", "apply Google style guide", "improve shell script", mentions "shellcheck", or discusses bash/shell...
GitHub
defense-in-depth
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. Validat...
GitHub
code-review-assistant
Perform systematic code review following {{sharedLib}}/{{projectName}} HMI standards and best practices. Use when reviewing pull requests, checking code quality, or validating implementations before commit. Che...
GitHub
implementation-doc-review
Review functional area and component documentation to check that it adheres to repo standards.
GitHub
feature-doc-review
Review a feature/component documentation to check that it adheres to repo standards.
GitHub
python-code-quality-scan
Run analyzer MCP tools (Ruff + optional dead-code scan) as a quality gate before QA/UAT/release.
GitHub
code-review
Automated code review for pull requests using specialized review patterns. Analyzes code for quality, security, performance, and best practices. Use when reviewing code changes, PRs, or doing code audits.
GitHub
ui-structure-lint
コンポーネントのディレクトリ構成、ファイル命名、コロケーション、およびインポート・エクスポートの規則を監査・矯正します。
GitHub
self-review
Self-review after code changes. Use proactively after completing any code modifications, before creating a pull request. Runs tests, checks code quality, and validates changes.
GitHub
code-reviewer
Expert code review skill for auditing code quality, security, performance, and maintainability. Use when (1) reviewing pull requests or code changes, (2) auditing existing code for issues, (3) validating code b...
GitHub
lint-docstrings
Review and fix docstrings to follow Google-style conventions. Use when asked to check docstrings, format docstrings, or lint docstrings.
GitHub
review
Review code for regressions, duplications, and spec compliance. Use after completing significant implementations, or when asked to verify work. Can be invoked proactively after major changes.
GitHub
enforce-file-limits
Enforce 500-line file size limits. Warn at 400 lines. Guide splitting large files into focused modules. Apply when writing or editing code.
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.