write-pr-comments

Post structured GitHub pull request review comments from Obsidian markdown notes.

2|Updated May 27, 2026
One-click install
npx skills add https://github.com/edlng/agents --skill write-pr-comments
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-pr-comments
Source: https://github.com/edlng/agents/tree/main/skills/claude/write-pr-comments
Command: npx skills add https://github.com/edlng/agents --skill write-pr-comments

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, python3.

What problem does it solve?

This skill bridges the gap between your local Obsidian-based code review notes and GitHub, allowing you to post structured, actionable feedback directly to a pull request without manual copy-pasting.

Core Features & Use Cases

  • Actionable Filtering: Automatically ignores non-actionable findings like "no change needed" or "matches existing pattern" to keep your reviews focused.
  • Smart Anchoring: Uses code evidence to verify line numbers against the actual PR diff, ensuring comments land on the correct lines even if the review note is slightly out of sync.
  • Tone Humanization: Automatically refines your review comments to sound professional, imperative, and concise, removing AI-generated filler.

Quick Start

Use the write-pr-comments skill to post the review findings from the Obsidian note named valkey-samples-feat-add-eino to the corresponding pull request.

Frequently Asked Questions about write-pr-comments

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

FAQPage Schema
How do I post code review comments from Obsidian notes directly to a GitHub pull request?

To post review comments from Obsidian markdown notes to a GitHub pull request, this skill parses your findings, verifies line anchors against the actual PR diff, and submits structured feedback directly through the GitHub CLI.

How does automated PR review anchoring handle outdated line numbers in markdown notes?

Automated PR review anchoring handles outdated line numbers by using code evidence to verify line numbers against the actual PR diff. This smart anchoring ensures comments land on the correct lines even if your review note is slightly out of sync.

Do I need the GitHub CLI and Python to automate pull request reviews from Obsidian?

Yes, you need the GitHub CLI and Python3 installed to automate pull request reviews from Obsidian. The skill requires GitHub CLI integration to execute API-based review submissions and Python3 to run its parsing and verification logic.

Can I filter out non-actionable findings when posting code review comments to GitHub?

Yes, you can filter out non-actionable findings when posting code review comments to GitHub. The skill automatically ignores findings like "no change needed" or "matches existing pattern" to keep your pull request reviews focused and actionable.

What is the best way to humanize the tone of automated code review comments on GitHub?

The best way to humanize automated code review comments is to refine review text to sound professional, imperative, and concise. This skill automatically removes AI-generated filler from your Obsidian notes before submitting them to the pull request.