GitHub
sonar-properties
Generates sonar-project.properties for SonarQube code quality analysis and coverage reporting. Auto-detects test framework (Jest/Vitest) and configures coverage paths.
☆ 0View skill
content media code quality AI Skills
Discover content media code quality skills, compare source repositories and read the instructions for each workflow.
Categories: content media code quality
content media code quality Clear filters
Browse skills
GitHub
prettier-config
Generates .prettierrc configuration file for code formatting with Prettier. Defines formatting rules for consistent code style across the project.
☆ 0View skill
GitHub
prettierignore
Generates .prettierignore to exclude build outputs, dependencies, and generated files from Prettier formatting. Prevents formatting of dist/, node_modules/, and coverage/ directories.
☆ 0View skill
GitHub
eslint-config
Generates ESLint 9+ configuration using flat config format. Creates eslint.config.cjs with Vue and TypeScript linting rules for code quality enforcement.
☆ 0View skill
GitHub
husky
Generates Husky Git hooks configuration with pre-commit checks. Creates .husky/pre-commit file for running linting, testing, and formatting before commits.
☆ 0View skill
GitHub
audit-code
Technical code review (architecture, type safety, patterns). Use for pre-merge review or general code quality audit.
☆ 0View skill
GitHub
audit-layout
Review layout consistency (spacing, alignment, grid usage). Use to ensure visual consistency across components.
☆ 0View skill
GitHub
audit-refactor-opportunities
Identify code smells and refactoring opportunities without fixing. Use for tech debt assessment.
☆ 0View skill
GitHub
security-scanning
This skill should be used when the user asks to "scan for vulnerabilities", "check for security issues", "find secrets in code", "audit dependencies", "detect SQL injection", "find XSS vulnerabilities", "check...
☆ 0View skill
GitHub
test-coverage
This skill should be used when the user asks to "analyze test coverage", "find untested code", "check coverage gaps", "improve test coverage", "identify missing tests", "measure code coverage", "test quality an...
☆ 0View skill
GitHub
receiving-code-review
Use when receiving code review feedback, processing PR comments, or needing to evaluate suggestions before implementing - requires technical verification not blind agreement
☆ 0View skill
GitHub
architecture-review
This skill should be used when the user asks to "review architecture", "analyze project structure", "check dependencies", "find circular imports", "analyze code patterns", "understand codebase structure", "map...
☆ 0View skill
GitHub
code-quality
This skill should be used when the user asks to "check code quality", "analyze code metrics", "find dead code", "check style compliance", "measure complexity", "find unused imports", "check type hints", "run li...
☆ 0View skill
GitHub
python-ruff-linter-formatter
Use ruff to lint, format, and modernize Python code. Activate when: (1) Fixing PEP 8 violations, (2) Removing unused imports, (3) Upgrading deprecated Python syntax (UP rules), (4) Auto-fixing code quality issu...
☆ 0View skill
GitHub
testing
Testing patterns and best practices for unit, integration, and E2E testing.
☆ 0View skill
GitHub
global-coding-style
Follow core coding style principles including SOLID, DRY, KISS, and YAGNI when writing code. Apply consistent naming conventions, meaningful variable names, small focused functions, automated formatting, and pr...
☆ 0View skill
GitHub
global-commenting
Write self-documenting code with clear structure and naming, using minimal but helpful comments only when necessary to explain complex logic. Use this skill across all code files when deciding whether to add co...
☆ 0View skill
GitHub
next-code-reviewer
Review code for adherence to project guidelines, style guides, and best practices. Use after writing or modifying code, before committing changes or creating pull requests.
☆ 0View skill
GitHub
next-type-design-analyzer
Analyze type design quality and invariants. Use when introducing new types, during PR creation with data models, or when refactoring type designs.
☆ 0View skill
GitHub
next-comment-analyzer
Analyze code comments for accuracy, completeness, and long-term maintainability. Use after adding documentation, before finalizing PRs with comment changes, or when reviewing existing comments for technical deb...
☆ 0View skill
GitHub
next-silent-failure-hunter
Identify silent failures, inadequate error handling, and inappropriate fallback behavior. Use when reviewing code with error handling, catch blocks, or fallback logic.
☆ 0View skill
GitHub
writing
Clear writing standards based on Zinsser's principles. Use for documentation, commit messages, PR descriptions, and technical communication.
☆ 0View skill
GitHub
reviewing-code
Code review workflow for evaluating changes against standards. Use when reviewing pull requests, commits, or diffs.
☆ 0View skill
GitHub
do-foundation-quality
TRUST 5 검증, 사전 분석, 자동화된 모범 사례 적용을 포함한 엔터프라이즈 코드 품질 오케스트레이터
☆ 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.