Loading...
Loading...
Found 955 Skills
Add, remove, or adjust Markuplint rules for specific files or elements. Analyzes violations, proposes scope-appropriate configuration changes, and confirms with the user.
Used for reviewing GitCode PRs, generating in-depth review conclusions or publishing line-by-line comments by combining PR metadata, diffs, and the context of the entire code repository. It is used when users want to review a GitCode PR, check a GitCode PR link, analyze change risks, or publish review comments to a GitCode PR. Typical trigger phrases include "review this PR", "inspect this PR", "check PR", or directly providing a GitCode PR link, such as https://gitcode.com/owner/repo/pull/123.
SonarCloud integration. Manage Projects. Use when the user wants to interact with SonarCloud data.
Detects code smells and anti-patterns — long methods, large classes, feature envy, data clumps, primitive obsession, dead code, magic numbers, deep nesting, and more. Uses configurable thresholds from .codeprobe-config.json when available. Trigger phrases: "code smells", "smell check", "anti-patterns", "clean code review".
Reviews code for quality, security, tests, and project standards (PEP 8, type hints, VERSION, Docker, funcoes.md). Use when reviewing pull requests, code changes, or when the user asks for a code review or quality check.
Organize functions in a file or across a branch.
Scan codebases for technical debt, score severity, track trends, and generate prioritized remediation plans. Use when users mention tech debt, code quality, refactoring priority, debt scoring, cleanup sprints, or code health assessment. Also use for legacy code modernization planning and maintenance cost estimation.
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
Use when reviewing code, pull requests, branches, diffs, or changed files for quality, correctness, security, performance, and style issues.
Use when writing, fixing, or editing TypeScript comments or TSDoc, especially commented-out code, stale docs, metadata comments, redundant comments, TODO banners, or unclear comment value.
Provides comprehensive code review guidance for React 19, Vue 3, Angular 17+, Svelte 5, Rust, TypeScript, Java, Python, Django, Go, C#/.NET, Kotlin, NestJS, C/C++, and more. Helps catch bugs, improve code quality, and give constructive feedback. Use when: reviewing pull requests, conducting PR reviews, code review, reviewing code changes, establishing review standards, mentoring developers, architecture reviews, security audits, checking code quality, finding bugs, giving feedback on code.
Run a final code review on a pull request