skills.rest
otahontas
otahontasCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

address-reviews

Process .review files and generate prioritized follow-up tasks.

1|Updated Jan 2, 2020
Search Tags:#automation#workflow#developer-tools#quality-assurance#code-review#review-files
One-click install
npx skills add https://github.com/otahontas/nix --skill address-reviews
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: address-reviews
Source: https://github.com/otahontas/nix/tree/main/home/configs/pi-coding-agent/skills/address-reviews
Command: npx skills add https://github.com/otahontas/nix --skill address-reviews

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams organize and act on code-review feedback by processing .review files created during local reviews, reducing manual effort and ensuring consistent follow-ups.

Core Features & Use Cases

  • Review file discovery: Finds and aggregates all .review files adjacent to their source files.
  • Prioritized workflow: Processes must-fix, then questions, then suggestions to drive timely fixes.
  • Actionable summaries: Generates clear, actionable items you can apply to code changes.

Quick Start

Run the review processor against a repository to process all .review files. For example:

  • Use this command to locate all reviews: find . -name "*.review" -type f 2>/dev/null
  • Review summaries can be applied by updating the corresponding source files or through your code editor.

Frequently Asked Questions about address-reviews

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

FAQPage Schema
How do I consolidate code-review feedback stored in local files?▼

Consolidating code-review feedback is done by discovering adjacent .review files in local repositories and aggregating them into a single structured workflow for must-fix, question, and suggestion items.

What is the best way to automate processing of .review files for code reviews?▼

Automating .review file processing involves locating all files in a local repository and generating actionable summaries that prioritize must-fix items, then questions, then suggestions.

Do I need external tools to process .review files in my local repository?▼

No external tools are required to process .review files beyond common shells, making it possible to generate actionable follow-ups directly within a local repository environment.

How does the prioritized workflow for code-review feedback handle different item types?▼

The prioritized workflow processes code-review feedback by addressing must-fix items first, then questions, and finally suggestions to drive timely fixes and clear actionable items.

Can I use shell commands to locate review files for code-review automation?▼

Yes, shell commands like 'find . -name "*.review" -type f' can locate review files in local repositories, enabling the processor to aggregate feedback and generate actionable follow-ups.

What limitations exist when consolidating .review files for code-review feedback?▼

Consolidating .review files is limited to local repositories and relies on common shells, meaning it does not integrate with external code-review platforms or require additional dependencies beyond the local environment.

Related Skills

Explore More Software Engineering Skills→
inference-siminference-sim
2

_summarize-problem-context

Aggregate context from repositories, URLs, and web searches into a research document.

Official
Advanced
cloudaura-iocloudaura-io
8

conductor:revert

Revert git commits for selected Conductor Tracks, Phases, or Tasks.

Official
Advanced
marcel-moremarcel-more
17

install-fm-xml-export-exploder

Clone and manage the fm-xml-export-exploder repository for FileMaker workflows.

Community
Intermediate
iliaaliliaal

file-todos

Manage development tasks and technical debt in Markdown files within a 'todos/' directory.

Community
Intermediate