remediation-options

Present standardized remediation options for config violations during repository audits.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/metasaver/claude-marketplace --skill remediation-options
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: remediation-options
Source: https://github.com/metasaver/claude-marketplace/tree/main/plugins/metasaver-core/skills/domain/remediation-options
Command: npx skills add https://github.com/metasaver/claude-marketplace --skill remediation-options

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When configuration violations are found, deciding how to address them (fix, ignore, or update the standard) requires careful consideration, especially in diverse monorepos. This skill automates the remediation decision process, guiding users to the most appropriate action.

Core Features & Use Cases

  • 3-Option Remediation Pattern: Presents standardized choices: Conform to template (fix repo), Ignore (skip violation), or Update template (evolve standard).
  • Smart Recommendations: Provides intelligent recommendations based on repository type (library vs. consumer) and violation severity (critical, warning, info).
  • User Interaction Pattern: Uses the AskUserQuestion tool to prompt for user choice and handles the execution of the selected remediation.
  • Exception Declaration Helper: Offers guidance on how to declare exceptions in package.json to permanently ignore specific violations.
  • Use Case: After an audit finds a missing ESLint rule, this skill will recommend "Conform to template" for a consumer repo, or "Ignore" for a library repo, guiding the user to the most appropriate action to maintain standards or acknowledge intentional differences.

Quick Start

Present remediation options for a critical ESLint violation in a consumer repository.

Frequently Asked Questions about remediation-options

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

FAQPage Schema
How do I handle configuration violations when auditing repositories?

Configuration violations can be addressed through three remediation options: conform the repository to the template standard, ignore the specific violation, or update the template itself. This skill automates presenting these options and guides you to the most appropriate action based on your repository type and violation severity.

What's the best way to decide between fixing a config issue or updating the standard?

Smart recommendations adapt to your repository context. Consumer repositories typically benefit from conforming to templates to maintain consistency, while libraries may warrant ignoring certain violations. The skill evaluates severity and repository type to recommend the optimal remediation path.

Can I permanently ignore specific configuration violations in my repository?

Yes. The skill provides guidance on declaring exceptions in package.json to permanently ignore specific violations without modifying the configuration itself, letting you maintain intentional differences while staying audit-compliant.

How do configuration remediation decisions work across monorepos with different project types?

The skill handles diverse monorepos by tailoring recommendations based on whether each project is a library or consumer application. After you select a remediation option, it triggers automatic re-audits to verify the change and ensure standards compliance across your codebase.

What happens after I choose a remediation option for a violation?

Once you select conform, ignore, or update template, the skill executes the chosen remediation and automatically re-audits your repository to confirm the violation is resolved and no new issues were introduced.