resolve-findings

Verify audit findings and document which issues require fixes.

9|1|Updated Jan 8, 2026
One-click install
npx skills add https://github.com/conn-castle/agent-layer --skill resolve-findings
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: resolve-findings
Source: https://github.com/conn-castle/agent-layer/tree/main/internal/templates/skills/resolve-findings
Command: npx skills add https://github.com/conn-castle/agent-layer --skill resolve-findings

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Triage review findings reports by verifying each item, determining which findings are accurate, and recording why others are not fixed, ensuring a reliable audit trail.

Core Features & Use Cases

  • Verifies each reported finding against the target codebase or plan artifacts.
  • Orchestrates multi-step triage: verify, decide, fix within scope, and document decisions.
  • Produces a resolution log and optional artifacts (plan, task, context) when fixes are accepted.

Quick Start

Review a findings report and begin triage by validating each item and selecting which to fix.

Frequently Asked Questions about resolve-findings

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

FAQPage Schema
How do I triage code review findings and decide which issues to fix?

Triage code review findings by verifying each reported item against the codebase, deciding which require fixes, and documenting the rationale for rejected items to ensure a reliable audit trail.

What is the best way to automate an audit trail for code review findings?

Automating an audit trail for code review findings involves orchestrating a multi-step workflow spanning verification, decision making, and documentation. This process generates a resolution log and ensures reproducible, documented outcomes for every triaged item.

How do I document why certain audit findings are not fixed?

Document why audit findings are not fixed by recording decision rationales during the triage workflow. The process verifies each finding against target artifacts, then explicitly logs the reasoning for rejected items alongside accepted fixes in the resolution log.

Can I generate a plan and task artifacts when accepting code review findings?

You can generate optional plan, task, and context artifacts when code review findings are accepted during triage. These artifacts ensure fixes are reproducible and properly scoped within the documentation workflow.

Does this triage workflow work with existing code-review pipelines?

The triage workflow applies directly to code-review pipelines by processing findings reports from audits. It verifies each reported issue against the target codebase or plan artifacts without requiring external dependencies.

When should I not use an automated triage workflow for review findings?

Avoid using an automated triage workflow for review findings when issues lack clear target codebase references or plan artifacts for verification. The process depends on validating each item against existing context to produce accurate decisions and a reliable audit trail.