system-refiner

Detect and correct project rules by applying atomic patches to relevant files.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Git-Fg/meta-plugin-manager --skill system-refiner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: system-refiner
Source: https://github.com/Git-Fg/meta-plugin-manager/tree/main/.claude/skills/system-refiner
Command: npx skills add https://github.com/Git-Fg/meta-plugin-manager --skill system-refiner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill autonomously detects and corrects misplaced or conflicting project rules when negative feedback is received, reducing recurrence of mistakes.

Core Features & Use Cases

  • Rule correction: Identify and rectify failing project rules, documentation notes, or procedural guidelines when user input indicates a mismatch.
  • Proactive patching: Apply targeted, atomic changes to existing rules or instructions to prevent recurrence.
  • Use Case: When a command or instruction conflicts with governance, patch the rule to align with policy.

Quick Start

Patch the offending rule by updating the relevant file in project docs.

Frequently Asked Questions about system-refiner

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

FAQPage Schema
How do I automate project rule correction when receiving negative feedback?

Automating project rule correction involves detecting negative feedback and applying targeted atomic patches to update the relevant governance files, documentation, or instructions in place to prevent recurrence.

What is the Delta Standard for patching project governance rules?

The Delta Standard is a patching approach used to apply targeted atomic changes to existing rules or instructions, ensuring that governance edits remain traceable and prevent recurrence.

How do I patch conflicting instructions to align with project governance policy?

You patch conflicting instructions by editing the offending rules and updating the relevant project documentation files to align with policy, ensuring all changes are documented for traceability.

Can I update skills and commands in place when a procedural rule fails?

Yes, you can update skills and commands in place by applying atomic patches to rectify failing procedural guidelines when user input indicates a mismatch or contradiction with project rules.

What is the best way to ensure traceability when revising project documentation?

To ensure traceability when revising project documentation, apply atomic patches following the Delta Standard and explicitly document the changes made to the relevant governance files.