How do I see all active warnings currently in effect?

You can list all active warnings by invoking the skill with the 'list' action or simply using the base trigger command.

Can I prevent Claude from using specific packages entirely?

Yes, by adding a package warning with the 'block' severity, you can instruct the system to treat that package as off-limits for the current project.

What is a 'grudge' in the context of this skill?

A grudge is a persistent warning attached to a specific file or package that alerts the AI to known issues, preventing it from making common mistakes or using suboptimal tools.

Are these warnings shared across different projects?

You can choose. Warnings can be set as 'repoSpecific' to only apply to the current directory, or global to follow you across all projects managed by Matrix.

Matrix Code Warnings

Name: Matrix Code Warnings
Author: ojowwalker77

byojowwalker77

•

Productivity & Workflow

Manages persistent warnings and technical debt 'grudges' for files and packages within the Claude Matrix ecosystem.

About

Matrix Warnings allows developers to establish a persistent memory of problematic code areas and deprecated dependencies, often referred to as 'personal grudges.' By setting custom warnings with varying severity levels (info, warn, or block), you can prevent Claude from inadvertently modifying fragile legacy files or introducing outdated packages into your projects. This skill provides a structured way to document technical debt and architectural constraints directly within the AI's workflow, ensuring that domain-specific knowledge about code quality is always respected during automated tasks.

Key Features

Instant auditing of files and packages via the check command
81 GitHub stars
Toggle between repository-specific or global cross-project warnings
Create persistent warnings for specific file patterns and package names
Assign severity levels including info, warn, and block to control AI behavior
Support for detailed reasoning to provide context for every warning

Use Cases

Documenting known bugs or technical debt in specific files to avoid recursive errors
Enforcing the migration away from deprecated libraries by flagging specific packages
Preventing the AI from modifying fragile legacy modules that require manual intervention

About

Key Features

Instant auditing of files and packages via the check command
81 GitHub stars
Toggle between repository-specific or global cross-project warnings
Create persistent warnings for specific file patterns and package names
Assign severity levels including info, warn, and block to control AI behavior
Support for detailed reasoning to provide context for every warning

Use Cases

Documenting known bugs or technical debt in specific files to avoid recursive errors
Enforcing the migration away from deprecated libraries by flagging specific packages
Preventing the AI from modifying fragile legacy modules that require manual intervention