GitHub
typescript-strict
Sets up TypeScript with strict type safety standards, including tsconfig.json with strict mode, ESLint rules, and type checking scripts. Use when starting a TypeScript project or enforcing type safety.
☆ 0View skill
blockchain code quality AI Skills
Discover blockchain code quality skills, compare source repositories and read the instructions for each workflow.
Categories: blockchain code quality
blockchain code quality Clear filters
Browse skills
GitHub
csharp-review
Code review against C# 14 standards. Four modes: standards, performance, architecture, full. Use for "/review", "check code", "performance review".
☆ 0View skill
GitHub
validator
Struct validation using tags for Go.
☆ 0View skill
GitHub
content-validator
Validate new campaign articles for template adherence, proper links, frontmatter compliance, and consistent style
☆ 0View skill
GitHub
code-review
Review code for team standards, security, and best practices
☆ 0View skill
GitHub
self-correction
Autonomously critique and verify code/logic before it reaches the user.
☆ 0View skill
GitHub
vscode-ext-commands
Guidelines for contributing commands in VS Code extensions. Indicates naming convention, visibility, localization and other relevant attributes, following VS Code extension development guidelines, libraries and...
☆ 0View skill
GitHub
build
Build, type-check, and lint the project
☆ 0View skill
GitHub
code-review
Perform a comprehensive code review
☆ 0View skill
GitHub
quality
Ensure code quality and correctness. Run tests, validation, and linters.
☆ 0View skill
GitHub
lsp-type-safety-check
Verify type safety of code changes using LSP hover and find-references.
☆ 0View skill
GitHub
acceptance-criteria
Generate Acceptance Criteria from code files. Use when user shares a code file and asks to write AC, acceptance criteria, or summarize what the code does for Jira tickets.
☆ 0View skill
GitHub
error-handling-standardizer
Standardize error formats and retry strategy.
☆ 0View skill
GitHub
security-auditor
Activates when user requests security review, penetration test analysis, sensitive data handling, authentication/authorization design, or OWASP risk assessment. Do NOT use for general code style reviews. Exampl...
☆ 0View skill
GitHub
nestjs-configuration
Environment variables validation and ConfigModule setup.
☆ 0View skill
GitHub
laravel-coding-standard
Activates when user writes or reviews PHP/Laravel code, requiring Laravel-specific coding standards validation. Do NOT use for basic indentation/whitespace checks (handled by linter). Examples: 'Check naming co...
☆ 0View skill
GitHub
review-shell-scripts
Review all shell scripts against the Bash Script Convention. Use when you need to check script compliance or before committing changes.
☆ 0View skill
GitHub
error-handling-standardization
Use this agent when standardizing error handling across the application with compassionate, user-friendly error messages. User: "Errors show technical jargon like '500 Internal Server Error'" Agent: Use error...
☆ 0View skill
GitHub
csharp-run
Run tests, lint, and build for .NET projects. Executes dotnet test with coverage, dotnet format check, and reports results. Use for "/run", "run tests", "check build", or "lint code".
☆ 0View skill
GitHub
typescript
TypeScript/JavaScript coding standards. Use when working on TS/JS code to ensure type safety, proper async handling, and clean code style.
☆ 0View skill
GitHub
readability-review
Code review focused on readability, maintainability, and clarity. Use after code changes, before merging, or when reviewing pull requests.
☆ 0View skill
GitHub
verify
Run code quality checks (lint, type check, tests). Use this after writing or modifying code to ensure quality.
☆ 0View skill
GitHub
verify
검증 스킬. 빌드, 린트, 테스트 검증. 커밋/PR 전 필수 실행. AI가 스스로 코드를 검증하는 자체 검증 루프.
☆ 0View skill
GitHub
code-review
Review code changes for correctness, security, tests, and architecture; use for code review or PR review requests (trigger keywords: code review, review changes, PR review, security review).
☆ 0View skill
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.