Address Findings
Address the review findings posted on an Entire trail: fetch the trail's open findings, fix the code, and resolve them on the trail. Use when the user gives a trail URL or number and asks to address, fix, or resolve its findings or review comments. Not for local diff review — that is the `review` skill.
Install
/plugin marketplace add entireio/skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add entireio/skills --skill address-findingsgit clone --depth 1 https://github.com/entireio/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/skills/address-findings ~/.claude/skills/address-findingsPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Address Findings Fix and resolve the open review findings on an Entire trail. A finding is a review comment posted to a trail on Entire: it has a file/line location, a body, a severity, and sometimes a suggested unified-diff patch. This skill fetches the open findings, applies or hand-fixes each one in the current worktree, and marks it resolved on the trail. ## When to use / not use Use when the user points at a trail — a trail or change URL such as `https://entire.com/<forge>/<project>/-/trails/<P>/changes/<repo>/<n>`, a bare trail number, or a branch name — and asks to **address / fix / resolve** its findings or review comments. Do **not** use this skill for: - A code review of the current diff — that is the `review` skill (read-only). - Creating new findings — use `entire trail finding add`. ## Response Format Begin the first response to this skill invocation with the line: `Entire Address Findings:` followed by a blank line, then the content. Apply the header to the **first response only**. Omit it on error / early-exit responses (CLI missing, not authenticated, trail not found, branch mismatch, no open findings). ## Rules 1. Make the smallest correct change that addresses each finding. Do not expand scope. 2. Only mark a finding resolved when you actually addressed it. If a finding is ambiguous or needs a human decision, leave it open and report it. 3. Do not commit or push. Leave changes in the working tree for the user to review.
Details
- Skill name
address-findings- Repository
- entireio/skills
- Path
skills/address-findings/SKILL.md- License
- MIT
- Repo updated
- 15 November 2026
FAQ
What does the Address Findings skill do?
Address the review findings posted on an Entire trail: fetch the trail's open findings, fix the code, and resolve them on the trail. Use when the user gives a trail URL or number and asks to address, fix, or resolve its findings or review comments. Not for local diff review — that is the `review` skill.
How do I install the Address Findings skill?
Claude Code plugin: /plugin marketplace add entireio/skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Address Findings popular?
It lives in entireio/skills, which has 240 GitHub stars and 28 forks.
Related skills
Explain
240entireio/skills
Explains the intent behind source code by finding original session transcripts. Use explain with a function, file, or line of code to understand why it exists.
Recall
240entireio/skills
Use when the user describes a task and wants to know whether something similar has been done before, then turn the closest prior session into a task playbook. Triggers on phrases like "have we done this before", "recall how we did X", "find similar work", "any precedent for", "has anyone solved", "is there a template for", and "how did we do this last time
Replay
240entireio/skills
Use when the user wants to step through a feature's checkpoints chronologically, pausing at each step to ask questions. Triggers on phrases like "replay <feature>", "walk me through how X was built", "show me the journey of", "step me through how Y was implemented", and "replay the last week
Clickup
132krodak/clickup-cli
Use when reading or changing anything in ClickUp via the `cup` CLI - tasks, sprints, comments, Docs, Chat, views, webhooks, or workspace structure. Triggers: task queries, status updates, sprint tracking, creating subtasks, posting comments, threaded replies, standup summaries, searching tasks, checking overdue items, assigning tasks, ClickUp Docs and doc pages (read, create, edit), ClickUp Chat channels and messages, views and view tasks, webhooks, exporting or archiving ClickUp data (knowledge transfer, off-boarding), creating or renaming spaces, folders, and lists, list templates, opening t
Code Reader V2 En
186notlate-cn/code-reader-skills
Cognitive science-based source code deep understanding assistant (English improved version). Supports 3 analysis modes: Quick (quick overview), Standard (standard understanding), Deep (deep mastery, auto-parallel for large projects). Combines elaborative interrogation, self-explanation testing, and retrieval practice to help truly understand and master code.
Codex
21623jmo/jmo-skills
Hand off a scoped implementation, code review, or technical second opinion to the OpenAI Codex CLI from Claude Code. Use when the user asks to delegate work to Codex or get an independent review.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.