Matrix Warnings
Scannednpx machina-cli add skill ojowwalker77/Claude-Matrix/warn --openclawMatrix Warnings
Manage "personal grudges" - warnings for problematic files or packages.
Parse user arguments from the skill invocation (text after the trigger phrase).
Use the matrix_warn tool with the appropriate action parameter.
Actions
List warnings (default, or "list"):
Use matrix_warn with action: "list" to show all warnings.
- Optional:
type: "file"ortype: "package"to filter - Optional:
repoOnly: trueto show only repo-specific warnings
Add warning ("add <type> <target> <reason>"):
Use matrix_warn with action: "add" and:
- type: "file" or "package"
- target: file path/pattern or package name
- reason: why this is problematic
- severity: "info", "warn", or "block" (default: warn)
- repoSpecific: true if warning should only apply to current repo
Remove warning ("remove <target>" or "rm <target>"):
Use matrix_warn with action: "remove" and either:
- id: the warning ID to remove, or
- type + target: to remove by type and target
Check target ("check <target>"):
Use matrix_warn with action: "check" and:
- type: "file" or "package"
- target: file path or package name
Examples
/matrix:warn- list all warnings/matrix:warn add file src/legacy/*.ts "Deprecated, do not modify"/matrix:warn add package moment "Use date-fns instead"/matrix:warn remove moment/matrix:warn check .env
Source
git clone https://github.com/ojowwalker77/Claude-Matrix/blob/main/skills/warn/SKILL.mdView on GitHub Overview
The Matrix Warnings skill lets you manage warnings for problematic files or packages. It supports listing, adding, removing, and checking warnings via the matrix_warn tool, helping teams enforce repository hygiene.
How This Skill Works
The skill parses the user’s intent from the trigger and calls matrix_warn with an action like list, add, remove, or check. You can filter by type (file or package), specify a target, provide a reason, and set severity. For removals, you can use an ID or specify type and target to remove the correct warning.
When to Use It
- View all current warnings to assess repository health.
- Add a file warning for deprecated or risky code paths with a reason.
- Add a package warning suggesting alternatives or updated usage.
- Remove a warning by its ID or by combining type and target after remediation.
- Check a specific file or package to confirm whether a warning exists.
Quick Start
- Step 1: Decide the action (list, add, remove, or check) and call /matrix:warn with that action.
- Step 2: If adding, provide type (file|package), target, reason, and optional severity and repoSpecific; if removing, provide id or type+target.
- Step 3: Verify the outcome by listing or checking the target to confirm the warning state.
Best Practices
- Use type: 'file' or 'package' to clearly categorize warnings.
- Include a clear reason and an appropriate severity (info, warn, block).
- Use repoSpecific: true when the warning should only apply to the current repository.
- Target precise paths, patterns, or package names to avoid ambiguity.
- Regularly review and prune stale warnings to keep signals meaningful.
Example Use Cases
- /matrix:warn - list all warnings
- /matrix:warn add file src/legacy/*.ts \"Deprecated, do not modify\"
- /matrix:warn add package moment \"Use date-fns instead\"
- /matrix:warn remove moment
- /matrix:warn check .env