vfs-reviewer

Awards-winning Israeli fintech startup specializing in AI-powered SaaS platforms for capital markets and beyond.

106|52|Updated Oct 29, 2010

Search Tags:#code review #pull request #security #github #java #vfs-s3

Ready to run

npx skills add https://github.com/abashev/vfs-s3 --skill vfs-reviewer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: vfs-reviewer
Source: https://github.com/abashev/vfs-s3/tree/main/.skills/vfs-reviewer
Command: npx skills add https://github.com/abashev/vfs-s3 --skill vfs-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of reviewing pull requests and code changes for the vfs-s3 project, ensuring code quality, correctness, and security.

Core Features & Use Cases

Automated Code Review: Analyzes code for bugs, security vulnerabilities, and adherence to coding standards.
PR Analysis: Can review both pull requests and standalone branches.
Constructive Feedback: Provides specific, actionable suggestions for improvement.
Use Case: When a developer submits a pull request to the vfs-s3 repository, this Skill can automatically assess the changes and provide a detailed review, flagging potential issues before they are merged.

Quick Start

Use the vfs-reviewer skill to review pull request number 185 for the vfs-s3 repository.

Frequently Asked Questions about vfs-reviewer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate pull request reviews for Java 17 code changes?▼

Automated Java 17 pull request review fetches PR details via the GitHub 'gh' CLI to analyze code changes for logic bugs, edge cases, resource leaks, thread safety, and security vulnerabilities. It then posts constructive, actionable feedback directly to the pull request.

Can I review standalone branches instead of just pull requests?▼

Yes, you can review standalone branches in addition to standard pull requests. The review process analyzes code changes on either standalone branches or active pull requests within the repository to check for correctness, quality, and security vulnerabilities.

Does the code review process check for thread safety and resource leaks?▼

Yes, the code review process explicitly checks for thread safety and resource leaks. It analyzes code changes to detect logic bugs, edge cases, error handling, Java 17 idioms, security vulnerabilities, test coverage, and style compliance.

What is the best way to check Java 17 idioms and style compliance in a PR?▼

The best way to check Java 17 idioms and style compliance in a PR is using an automated review process that analyzes code changes. This approach flags deviations from coding standards and provides specific, actionable suggestions for improvement before merging.

Do I need the GitHub CLI to automate code security reviews?▼

Yes, you need the GitHub 'gh' CLI to automate code security reviews for this workflow. The review process integrates with GitHub via the 'gh' CLI specifically to fetch pull request details and post the resulting security and quality assessments.