remediation

Parse pipeline findings into uniform remediation records and tracked tickets.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/djwmobley/pipeline --skill remediation-djwmobley
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: remediation
Source: https://github.com/djwmobley/pipeline/tree/main/skills/remediation
Command: npx skills add https://github.com/djwmobley/pipeline --skill remediation-djwmobley

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bridges the gap between discovering findings and implementing fixes by enabling cross-pipeline remediation: red team, audit, review, UI, and external reports produce tracked tickets, dispatched stateless implementer/reviewer agents, and verified fixes.

Core Features & Use Cases

  • Uniform Artifact Model: all sources produce identical records with fields like ID, SEVERITY, CONFIDENCE, LOCATION, CATEGORY, DESCRIPTION, IMPACT, REMEDIATION, EFFORT, VERIFICATION_DOMAIN.
  • Ticket-driven context store: agents read and write only by ticket reference, enabling stateless orchestration.
  • End-to-end process: triage, ticket creation, plan, execution, and verification across multiple source types.
  • Verification strategies: per-source re-runs (redteam purple, audit sector, review re-run, ui-review), ensuring fixes are validated before closure.
  • Atomic fixes: one finding per commit with clear rollbacks and traceability.
  • Non-intentional flags: support for INTENTIONAL markings and non_negotiable decisions to suppress auto-issue creation when needed. Use cases: applicable to security findings, compliance gaps, or quality issues across pipelines.

Quick Start

Provide triage output to remediation to kick off ticket creation, assignment, and automated verification.

Frequently Asked Questions about remediation

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

FAQPage Schema
How do I automate remediation for security findings across multiple pipelines?

Automated remediation parses findings from any pipeline into uniform records and creates tracked tickets. It dispatches stateless implementer and reviewer agents to drive fixes and perform per-source verification.

What is the best way to orchestrate ticket-driven remediation for audit and review findings?

Ticket-driven remediation uses a context store where agents read and write only by ticket reference. This enables stateless orchestration and ensures end-to-end traceability for audit and review findings.

How do I standardize findings from red team, audit, and UI reviews into a uniform format?

Standardizing findings uses a uniform artifact model with fields like ID, SEVERITY, CONFIDENCE, LOCATION, CATEGORY, DESCRIPTION, IMPACT, REMEDIATION, EFFORT, and VERIFICATION_DOMAIN across all sources.

Can I suppress automatic ticket creation for intentional or non-negotiable security findings?

Yes, you can suppress automatic ticket creation for intentional findings. The system supports INTENTIONAL markings and non_negotiable decisions to prevent auto-issue creation when needed.

How does per-source verification work when closing remediation tickets?

Per-source verification re-runs specific checks before closing tickets. Strategies include redteam purple, audit sector, review re-run, and ui-review to validate fixes against the original finding source.

What is the process for ensuring atomic fixes during pipeline remediation?

Atomic fixes enforce one finding per commit to ensure clear rollbacks and traceability. This approach maintains end-to-end process integrity from triage and ticket creation through execution and verification.