GitHub
the-linter
Identifies and fixes ESLint errors and TypeScript type issues across the codebase.
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
quality-detect-regressions
Compares current quality metrics (tests, coverage, type errors, linting, dead code) to baseline and detects regressions. PROACTIVELY invoked after task completion, before marking task complete, or before mergin...
GitHub
linter-error-prevention
Enforces zero linter errors, common issue prevention, code cleanup. Use when writing code, reviewing code, or ensuring code quality standards.
GitHub
quality-capture-baseline
Captures quality metrics baseline (tests, coverage, type errors, linting) by running quality gates and storing results in memory. PROACTIVELY invoked at feature start, before refactor work, or after major chang...
GitHub
preview-smoke-testing
Run preview build smoke tests and verify runtime config. Use when the user mentions preview smoke, runtime config validation, or pre‑deploy checks.
GitHub
treido-audit
Audit/checklist skill for Treido (security, perf, i18n, UI consistency, docs drift). Triggers on "AUDIT:" prefix or when asked to review/scan for issues.
GitHub
architecture-single-responsibility-principle
Automated SRP validation using multi-dimensional detection. Use when reviewing code for SRP compliance, checking "is this doing too much", validating architectural boundaries, before commits, or during refactor...
GitHub
architecture-validate-srp
Detect Single Responsibility Principle (SRP) violations using multi-dimensional analysis. Use when reviewing code for "SRP", "single responsibility", "god class", "doing too much", "too many dependencies", befo...
GitHub
audit
Run an interactive codebase audit to analyze project structure, detect issues, and generate improvement PRDs. Use when you want to understand a codebase, find technical debt, or plan improvements. Triggers on:...
GitHub
code-documentation-standards
Enforces Dart doc comments for public APIs, parameter descriptions, usage examples. Use when writing public APIs, reviewing code, or ensuring documentation completeness.
GitHub
code-review-checklist
Code review guidelines covering code quality, security, and best practices.
GitHub
the-auditor
Audits the codebase for security vulnerabilities and regulatory compliance (LGPD, GDPR, DORA, MiCA, HIPAA, SOC II, ISO 27001, PCI-DSS).
GitHub
nix-cleanup
Run janitorial cleanup for this flake: flake check, statix/deadnix linting, and safe hygiene fixes.
GitHub
tailwind-style-guidelines
Enforces consistent Tailwind CSS usage, preventing utility abuse and visual inconsistency.
GitHub
lang-ts
TypeScript/JavaScript conventions and reliability checklist for agents (build, typecheck, tests).
GitHub
receiving-code-review
当收到代码审查反馈时使用，在实施建议之前，特别是如果反馈似乎不清楚或技术上可疑时 - 需要技术严谨性和验证，而不是表演性同意或盲目实施
GitHub
run
Run the current project based on detected language
GitHub
typescript-configuration
TypeScript configuration standards and tsconfig.json patterns
GitHub
code-review
Code review checklist for changes made by an agent.
GitHub
safe-editing
Best practices for making safe, verified code edits
GitHub
architecting-structure
Enforces "Feature-First" architecture across standard frameworks. Use to scaffold new projects, refactor messy ones, or enforce clean file organization rules.
GitHub
code-review-assist
コード品質チェックと改善提案。Lintエラー修正、未使用コード削除、リファクタリング時に使用。警告、unused、refactor時に使用。
GitHub
quality-detect-refactor-markers
Finds all REFACTOR markers in codebase, validates associated ADRs exist, identifies stale markers (30+ days old), and detects orphaned markers (no ADR). Use during status checks, before feature completion, or f...
GitHub
coding-best-practices
General coding principles for writing clean, maintainable code. Triggers on any development work, code reviews, refactoring, or when adding dependencies. For frontend/React code, also apply web-ui-best-practice...
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é.