Identify security vulnerabilities, logic errors, and quality issues in code changes.
npx skills add https://github.com/DVNghiem/FlowDeck --skill code-review-dvnghiem
Please help me install this Agent Skill. Skill: code-review Source: https://github.com/DVNghiem/FlowDeck/tree/main/src/skills/code-review Command: npx skills add https://github.com/DVNghiem/FlowDeck --skill code-review-dvnghiem
Code review is essential to catch security vulnerabilities, logic errors, and quality issues before they reach production, reducing risk and rework.
Review the latest commit for security and quality issues and return a prioritized remediation plan.
High-intent search queries and answers about installing and using this skill.
Detect security vulnerabilities in code changes by analyzing touched files during pull requests or commits. This process identifies confirmed risks, ranks them by severity, and provides actionable remediation steps to prevent issues from reaching production.
Static analysis for bug detection during pull request reviews evaluates modified source code to identify logic errors and quality issues. It targets only the touched files to speed up feedback and outputs a severity-ranked list of confirmed problems with guidance for fixes.
Automated code review supports pre-push checks and CI gates by assessing changed files for security vulnerabilities and quality issues. It ensures only confirmed issues are flagged and delivers prioritized remediation plans to block problematic code from integration.
Get a prioritized remediation plan for logic errors by running a code review on your latest commit. The analysis assesses the touched files, confirms the existence of logic errors and quality issues, and outputs ranked, actionable steps to guide your fixes.
Automated code review minimizes false positives during quality assurance checks by ensuring only confirmed security vulnerabilities and logic errors are flagged. It focuses strictly on identified issues in touched files and provides clear remediation guidance rather than speculative warnings.
The best way to catch quality issues in a typical software project is targeted code review during changes. By analyzing touched files in pull requests and pre-push validations, you receive severity-ranked outputs with actionable steps to fix confirmed problems early.
AvatarGanymedeSynchronize .kandev/ configuration files to the office database.
jaisonerickReproduce QA-reported failures with failing tests and apply minimal code fixes.
FaisalAlqarniAutomate build, static analysis, testing, and security scanning for Spring Boot projects.
DevHive1Orchestrate dependency, static analysis, and privacy dataflow scanners into prioritized reports.
