diffity-resolve-tree

Apply code fixes to repository files to resolve open tree-browser comments.

739|50|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/nilbuild/diffity --skill diffity-resolve-tree-nilbuild
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diffity-resolve-tree
Source: https://github.com/nilbuild/diffity/tree/main/packages/skills/diffity-resolve-tree
Command: npx skills add https://github.com/nilbuild/diffity --skill diffity-resolve-tree-nilbuild

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Open comments left on repository files via the diffity tree browser, enabling you to automatically apply requested code changes and keep reviews moving.

Core Features & Use Cases

  • Read open threads from the tree browser and extract actionable requests.
  • Apply targeted code changes across multiple files to resolve threads.
  • Summarize and report resolutions back to the tree interface for auditability.

Quick Start

Tell your agent to resolve a thread by its ID using the diffity tree workflow and verify the changes in the browser.

Frequently Asked Questions about diffity-resolve-tree

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

FAQPage Schema
How do I automatically resolve code review comments on repository files?

Automatically resolving code review comments involves reading open threads from the tree browser, interpreting user requests, applying targeted code changes across multiple files, and summarizing resolutions back to the interface for auditability.

What is the best way to apply targeted code fixes across multiple files from a tree browser?

Applying targeted code fixes from a tree browser requires a workflow that extracts actionable requests from open threads, modifies the source files accordingly, and reports the outcomes back to the UI to keep reviews moving.

Can I resolve multi-thread reviews and apply code changes end-to-end in a repository?

You can resolve multi-thread reviews by targeting open comments across the diffity tree interface, interpreting the requested code changes, modifying the source files, and reporting the final outcomes back to the tree UI.

How do I start resolving a specific thread by its ID in the diffity tree workflow?

To start resolving a thread, tell your agent to resolve the thread by its ID using the diffity tree workflow, then verify the applied code changes directly in the tree browser interface.

Does automating repository comment resolution work for multi-thread reviews without manual file editing?

Automating repository comment resolution works for multi-thread reviews by directly applying requested code changes to repository files without manual editing, summarizing and reporting the resolutions back to the tree interface.