skills.rest
try-works
try-worksCOMMUNITY
Explore all skills by this author →
Website𝕏@trydotworksGitHub

reconcile-code-review

Reconcile code review findings against previous reviews and human comments.

95|4|Updated Apr 12, 2026
Search Tags:#code review#issue tracking#reconciliation#automated analysis#issue classification
One-click install
npx skills add https://github.com/try-works/role-model --skill reconcile-code-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reconcile-code-review
Source: https://github.com/try-works/role-model/tree/main/.agents/skills/reconcile-code-review
Command: npx skills add https://github.com/try-works/role-model --skill reconcile-code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the reconciliation of code review findings against previous reviews and human comments, streamlining the process of identifying and classifying issues.

Core Features & Use Cases

  • Automated Reconciliation: Matches current code review findings with previous reviews and human comments.
  • Issue Classification: Classifies issues as 'active', 'ignored_by_reviewer', or 'resolved'.
  • Use Case: Ideal for developers and project managers who need to efficiently manage and track code review issues in a repository.

Quick Start

Run the reconcile-code-review skill on the latest code review findings to automatically classify issues.

Frequently Asked Questions about reconcile-code-review

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

FAQPage Schema
How do I automate code review reconciliation against previous findings?▼

Automate code review reconciliation by running the skill on current findings to match them against previous reviews and human comments, classifying issues as active, ignored, or resolved.

What is code review issue classification and how does it work?▼

Code review issue classification categorizes current findings by comparing them with previous review data and human comments to label issues as active, ignored_by_reviewer, or resolved.

Can I track ignored or resolved code review issues automatically?▼

Yes, you can track ignored or resolved code review issues automatically by analyzing current code review data and comparing it with human feedback to classify the status of each issue.

What is the best way to match current code review findings with previous reviews?▼

The best way to match current code review findings with previous reviews is to use automated analysis that compares current findings against historical review data and human comments.

Do I need human comments to classify code review issues?▼

Human comments are required for code review issue classification because the skill compares current findings against previous review data and human feedback to determine if issues are active, ignored, or resolved.

Why are some code review issues marked as ignored_by_reviewer?▼

Code review issues are marked as ignored_by_reviewer when the automated analysis of current findings, previous review data, and human comments indicates the reviewer intentionally bypassed the issue.

Related Skills

Explore More Software Engineering Skills→
bitwardenbitwarden
129

reviewing-incremental-changes

Re-review only changed lines in pull requests after developer updates.

Official
Basic
strawgatestrawgate

find-stale-issues

Identify stale, resolved, or duplicate GitHub issues via semantic similarity analysis.

Community
Advanced
robertbr123robertbr123

requesting-code-review

Automate code review with security scans, quality checks, and automated fixes.

Community
Advanced
lklimeklklimek
1

triage-findings

Classify code review findings in a browser and update report.json.

Community
Advanced