pending-remediation-executor

Parse the remediation matrix CSV and update statuses with completion notes.

Updated Apr 25, 2026
One-click install
npx skills add https://github.com/raulbellosom/Atlas-ERP --skill pending-remediation-executor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pending-remediation-executor
Source: https://github.com/raulbellosom/Atlas-ERP/tree/main/.roo/skills/pending-remediation-executor
Command: npx skills add https://github.com/raulbellosom/Atlas-ERP --skill pending-remediation-executor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Systematically address bugs listed in the pending-remediation-matrix.csv by providing a repeatable workflow to triage, fix, update statuses, and provide audit evidence. This skill helps teams move remediation work from backlog to closed items with traceable actions.

Core Features & Use Cases

  • Parse and cross-reference the pending remediation matrix to identify open remediation tasks.
  • Read the master remediation context documents to gather context and dependencies.
  • Determine affected application (API, Web, Desktop, Worker) and select an appropriate fix strategy.
  • Update the remediation CSV with status changes and add completion notes for traceability.
  • Produce an execution summary to facilitate audits and progress reporting.

Quick Start

Run the remediation script to process the pending remediation matrix and update statuses accordingly.

Frequently Asked Questions about pending-remediation-executor

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

FAQPage Schema
How do I automate bug triage and update remediation statuses from a CSV backlog?

Automating bug triage requires parsing the pending remediation matrix CSV, selecting a fix strategy from FIX_STRATEGIES.md, applying the fix, and logging completion notes back into the CSV for traceable audit evidence.

What is the process for closing backlog bugs across API, Web, Desktop, and Worker components?

Closing backlog bugs involves identifying the affected application area, selecting an appropriate fix strategy, applying the fix, and updating the remediation matrix CSV with status transitions and audit logging notes.

How do I enforce remediation governance and status transitions when fixing a bug backlog?

Enforcing remediation governance requires following the remediation-master guidance, executing status transitions correctly, and satisfying audit logging requirements while updating the remediation matrix CSV with completion notes.

Can I use a CSV file to track pending remediation tasks and generate an audit summary?

Yes, you can use a pending remediation matrix CSV to track open tasks, update statuses as fixes are applied, and produce an execution summary that facilitates audits and progress reporting.

How do I select the right fix strategy when processing a remediation backlog?

Selecting a fix strategy requires determining the affected application component, consulting the FIX_STRATEGIES.md document for appropriate options, and applying the chosen strategy to resolve the specific backlog item.