skills.rest
vinhnxv
vinhnxvCOMMUNITY
Explore all skills by this author →
𝕏@vinhnxvGitHub

post-findings

Post structured review findings from a TOME to a GitHub PR.

6|3|Updated Feb 11, 2026
Search Tags:#automation#markdown#github#pr#findings#post#tome
One-click install
npx skills add https://github.com/vinhnxv/rune --skill post-findings
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: post-findings
Source: https://github.com/vinhnxv/rune/tree/main/plugins/rune/skills/post-findings
Command: npx skills add https://github.com/vinhnxv/rune --skill post-findings

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post Rune review findings to a GitHub PR from a TOME file as a formatted, collapsible comment, reducing manual effort and ensuring consistency. It parses structured findings, formats them for readability, and posts to the PR via the GitHub API with idempotency markers and optional dry-run support.

Core Features & Use Cases

  • Auto-detect latest TOME or explicit path; format findings for PR comments.
  • Collapsible markdown formatting for tidy review summaries.
  • Dry-run preview and idempotent posting to prevent duplicates.
  • Use case: after /rune:arc or /rune:appraise to share findings with the team.

Quick Start

Provide a TOME path and PR number, then invoke the skill to post findings to the PR.

Frequently Asked Questions about post-findings

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

FAQPage Schema
How do I post code review findings to a GitHub PR as a comment?▼

To post code review findings to a GitHub PR, this Skill parses structured findings from a TOME file, formats them into collapsible markdown, and posts them via the GitHub API. It auto-detects the latest TOME and PR to automate the workflow.

What is a TOME file for GitHub PR automation?▼

A TOME file is a structured format used to store code review findings. This Skill reads the TOME file, extracts the review findings, and converts them into formatted markdown for posting directly to a GitHub pull request.

Can I preview PR comments before posting them to GitHub?▼

Yes, you can preview PR comments before posting by using the dry-run support feature. This allows you to see exactly how the structured findings will be formatted in collapsible markdown without actually posting to the GitHub API.

How do I prevent duplicate findings comments on a GitHub PR?▼

To prevent duplicate findings comments on a GitHub PR, this Skill uses an idempotent marker. This ensures that repeated invocations do not post the same review findings multiple times, keeping the PR discussion clean.

Does the PR posting automation support force posting for stale comments?▼

Yes, the PR posting automation supports force posting when needed. Alongside the idempotent marker, this feature allows you to override existing checks and update the GitHub PR with new collapsible markdown findings.

Related Skills

Explore More Software Engineering Skills→
tusosostusosos

invoice-organizer

Extract invoice data, rename files, and generate CSV summaries.

Community
Intermediate
alistairsteadalistairstead

gh-pr-comments

List unresolved GitHub PR review comments and resolve threads by thread_id.

Community
Advanced
NooBatNooBat

review-pr

Automate GitHub pull request reviews with inline comments.

Community
Intermediate
John2143John2143
2

gh-triage

Automate triage of GitHub Pull Request review comments by filtering false positives.

Community
Intermediate