inline-review

Convert structured JSON review findings into inline GitHub Pull Request comments.

4|Updated May 1, 2026

Search Tags:#code review #pull request #github #automated review #inline comments

Ready to run

npx skills add https://github.com/HigorAlves/orc --skill inline-review

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: inline-review
Source: https://github.com/HigorAlves/orc/tree/main/orc/skills/inline-review
Command: npx skills add https://github.com/HigorAlves/orc --skill inline-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enables automated conversion of structured review findings into detailed inline comments directly on GitHub pull requests, streamlining the code review process.

Core Features & Use Cases

Structured Findings Conversion: Transforms JSON-formatted review findings into inline comments anchored to specific files and lines.
Event Determination: Computes the appropriate review event (APPROVE, COMMENT, REQUEST_CHANGES) based on severity rules.
Use Case: When an agent detects bugs or security issues in code, use this Skill to generate precise inline comments that are posted directly in the PR for immediate developer action.

Quick Start

Invoke the skill with a JSON report of findings to automatically generate and post inline GitHub comments targeting the affected lines.

Frequently Asked Questions about inline-review

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

FAQPage Schema

How do I convert structured code review findings into inline GitHub PR comments?▼

You can convert structured JSON review findings into inline GitHub PR comments by using a skill that anchors feedback to specific files and lines, computing the appropriate review event based on severity rules.

Can I automatically approve or request changes on a GitHub pull request based on code severity?▼

Yes, automated review event determination computes the appropriate GitHub PR event (APPROVE, COMMENT, or REQUEST_CHANGES) dynamically based on the severity rules defined in your structured review findings.

What is the best way to post automated code review comments directly to affected lines in a GitHub PR?▼

The best way to post automated code review comments to affected lines is to pass a JSON report of findings to a conversion tool that anchors them precisely to specific file paths and line numbers in the pull request.

How do I format structured findings so they can be posted as inline comments on a pull request?▼

You need to format your structured findings as a JSON report containing the file path, line number, severity, and review message, which the skill then maps to GitHub's inline comment anchoring system.

Do I need any external dependencies or modules to generate inline GitHub comments from review findings?▼

No external dependencies are required to generate inline GitHub comments from review findings, as the skill operates independently using its internal references to map structured data to the pull request API.

When should I use inline PR comments instead of general summary comments for automated code review?▼

You should use inline PR comments instead of general summary comments when your automated agent detects specific bugs or security issues that require precise file-line anchoring for immediate developer action.