address-findings

Fetches open review findings from an Entire trail, fixes the code, and resolves them.

Updated Aug 22, 2026
One-click install
npx skills add https://github.com/squidllee/skills --skill address-findings-squidllee
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: address-findings
Source: https://github.com/squidllee/skills/tree/main/address-findings
Command: npx skills add https://github.com/squidllee/skills --skill address-findings-squidllee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Review findings posted on an Entire trail require manual back-and-forth: reading each comment, locating the code, making the fix, and marking it resolved. This Skill automates that loop by fetching open findings, applying suggested patches or making targeted edits, and resolving findings on the trail. ## Core Features & Use Cases - Fetch and triage findings: Lists open findings for a trail via the Entire CLI, ordered by severity (high to low), with file/line locations and suggested unified-diff patches. - Apply or hand-fix: Dry-runs suggested patches with --check, applies and resolves them in one step, or makes the smallest correct manual edit when no patch exists. - Branch safety guard: Verifies you are on the trail's branch before editing the worktree, and stops with checkout instructions if not. - Use Case: A teammate's review left five findings on trail 42. Run this Skill with the trail URL to apply three suggested patches, manually fix one ambiguous comment, and leave one design decision open with a report. ## Quick Start Ask the assistant to address the open findings on trail https://entire.io/github/acme/app/trails/42 using the address-findings skill.

Frequently Asked Questions about address-findings

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

FAQPage Schema
How do I resolve review findings on an Entire trail?▼

Provide the trail URL or number and ask to address its findings. The skill runs `entire trail finding list` to fetch open findings, applies suggested patches with `entire trail finding apply --resolve`, or manually edits the code and resolves each finding with a message.

What is the difference between the address-findings and review skills?▼

The review skill performs a read-only code review of the current diff, while address-findings modifies the worktree to fix existing findings posted on a trail and marks them resolved. Use review for new analysis and address-findings for acting on existing comments.

Does address-findings commit or push the fixes?▼

No, it never commits or pushes. All changes stay in the working tree so you can review them yourself before committing, and the final report reminds you the changes are uncommitted.

Why does address-findings stop with a branch mismatch error?▼

Because `entire trail finding apply` edits the local worktree, the skill verifies your current branch matches the trail's branch first. If they differ, it stops and tells you to run `entire trail checkout <trail>` before re-running.

What happens when a suggested patch does not apply cleanly?▼

The skill dry-runs each patch with `--check` first. If it conflicts, it falls back to reading the finding and making a minimal manual edit; if the fix is ambiguous or needs a product decision, it leaves the finding open and reports it.