Review staged git changes, pull requests, and commit ranges for bugs and security issues.
npx skills add https://github.com/vulikjulik/DeepLom --skill aif-review-vulikjulik
Please help me install this Agent Skill. Skill: aif-review Source: https://github.com/vulikjulik/DeepLom/tree/main/.opencode/skills/aif-review Command: npx skills add https://github.com/vulikjulik/DeepLom --skill aif-review-vulikjulik
This Skill eliminates the tedious and error-prone process of manually reviewing code changes, pull requests, and commit histories, ensuring consistent code quality, security, and adherence to project standards without missing critical issues.
Ask the AI to review your staged code changes for bugs, security flaws, and adherence to your project's coding standards.
High-intent search queries and answers about installing and using this skill.
Automate code reviews for GitHub pull requests by passing the PR number or URL to identify bugs, security vulnerabilities, and performance issues. The review uses the GitHub CLI to access PR data and evaluate changes against project-specific coding conventions.
Yes, you can check staged local changes for bugs before committing by running an automated pre-commit validation. This process retrieves local git diffs to detect deviations from coding best practices and security flaws prior to pushing to a remote branch.
Audit a commit history range against coding best practices by specifying a commit range relative to any git reference. This evaluates commit quality, checks for boundary violations, and ensures architectural rules are consistently enforced across the history.
Yes, automated code review works with project-specific architecture rules by integrating with project context artifacts. This allows the review process to catch boundary violations and flag changes that misalign with your team's established roadmap milestones and coding conventions.
The best way to find security vulnerabilities in a pull request is through automated security checks integrated into your workflow. This evaluates the PR diff for security flaws and performance bottlenecks before merging, ensuring consistent code quality without manual inspection.
Yes, you need the GitHub CLI to perform a pull request audit because the review process integrates with it to access PR data. Local staged change reviews and commit range checks solely require git for retrieving diffs.
chcardozPush a local Git branch and create a GitHub pull request.
marinkobabicAutomate code reviews on staged changes, pull requests, and commit ranges.
prof-danielcRun static analysis tools and aggregate results into a prioritized issue report.
himanshu231204Run automated verification checks for Django applications before code review or deployment.
