001-lint

Review code changes against XDR Decision Records and report violations.

1|1|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/flaviostutz/agentkit --skill 001-lint
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 001-lint
Source: https://github.com/flaviostutz/agentkit/tree/main/examples/.xdrs/_core/adrs/principles/skills/001-lint
Command: npx skills add https://github.com/flaviostutz/agentkit --skill 001-lint

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures code quality and compliance by automatically reviewing changes against established Decision Records (XDRs), identifying and reporting violations without altering the code itself.

Core Features & Use Cases

  • Automated Code Review: Scans code against defined XDR rules.
  • Compliance Reporting: Identifies and categorizes violations as ERRORs or WARNINGs.
  • Use Case: Before merging a pull request, use this Skill to automatically check if the new code adheres to all architectural and quality standards documented in the repository's XDRs.

Quick Start

Run a code review against the latest changes in the main branch.

Frequently Asked Questions about 001-lint

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

FAQPage Schema
How do I audit code against architectural decision records before merging?

To audit code against decision records (XDRs), this Skill analyzes diffs or file contents, compiles applicable XDRs from the repository, and cross-references the code to identify violations. It outputs structured findings categorized by severity (ERROR/WARNING) without altering the code itself.

What is XDR compliance checking in a code review workflow?

XDR compliance checking is the process of scanning code changes against established Decision Records to ensure architectural and quality standards are met. This Skill automates this by cross-referencing diffs against repository XDRs and reporting violations as structured findings.

Can I use this Skill to check pull request diffs for decision record violations?

Yes, you can use this Skill to check pull request diffs for decision record violations. It analyzes the latest changes against the repository's compiled XDRs and classifies any architectural or quality standard deviations as ERRORs or WARNINGs.

How does automated code auditing handle XDR violation reporting?

Automated code auditing handles XDR violation reporting by outputting a structured report that categorizes findings by severity, specifically ERROR or WARNING. The report provides specific references to the violated rules and offers suggestions for fixes.