xdrs-core 0.2.15 → 0.2.16

package/.xdrs/_core/adrs/principles/001-xdr-standards.md

@@ -137,4 +137,4 @@ In the end, state explicitly the question that needs to be answered. E.g: "Which
 
 ## References
 
-- [001-xdr-lint skill](skills/001-xdr-lint/SKILL.md) - Skill for reviewing code changes against XDRs
+- [001-lint skill](skills/001-lint/SKILL.md) - Skill for reviewing code changes against XDRs

package/.xdrs/_core/adrs/principles/skills/{001-xdr-lint → 001-lint}/SKILL.md

@@ -1,9 +1,8 @@
 ---
-name: 001-xdr-lint
+name: 001-lint
 description: >
-  Reviews code changes or files against applicable XDRs (Decision Records) and reports
-  violations as structured findings. Activate this skill when the user asks to review,
-  lint, or audit code, or when you identify a need to check compliance with XDRs during implementation.
+  Reviews code changes or files against applicable XDRs (Decision Records) and reports violations as structured findings. 
+  Activate this skill when the user asks to review, lint, or audit code, or when you identify a need to check compliance with XDRs during implementation.
 metadata:
   author: flaviostutz
   version: "1.0"
@@ -11,8 +10,7 @@ metadata:
 
 ## Overview
 
-Performs a structured review of code changes or files against the XDRs in the repository,
-categorizing findings by severity and type, and reporting them without modifying any code.
+Performs a structured review of code changes or files against the XDRs in the repository, categorizing findings by severity and type, and reporting them without modifying any code.
 
 ## Instructions
 
@@ -43,7 +41,7 @@ categorizing findings by severity and type, and reporting them without modifying
 3. For related XDRs and files, lookup for the specific line number in both the XDR and the code that are related to the finding. This will be used in the reporting phase to provide precise references and actionable suggestions.
 
 ### Phase 4: Judgment
-3. Judgment criteria (all must be true to keep a finding):
+1. Judgment criteria (all must be true to keep a finding):
    - Is the violation explicitly stated as a rule in an Accepted XDR using mandatory or advisory language? Templates, examples, and diagrams in XDRs are illustrative only — they do not constitute rules. If the only evidence for the violation is an implicit pattern in a code sample or template, drop it.
    - Is there concrete evidence in the code or diff?
    - Is the finding actionable?
@@ -51,56 +49,37 @@ categorizing findings by severity and type, and reporting them without modifying
 
 ### Phase 5: Reporting
 
-Format each finding as:
-
-```
->> [ERROR|WARNING] [CATEGORY] [filename:line_number](filename#Lline_number): Description
-   - XDR Reference: [.xdrs/scope/type/subject/number-title.md:line_number](.xdrs/scope/type/subject/number-title.md#Lline_number)
-   - Rule: Specific rule text from XDR
-   - Severity: [ERROR|WARNING]
-   - Suggestion: Specific action to fix this issue
-   - Context: Why this matters / What to watch for
-```
-
-Full output structure:
-
-```
-=== Code Review Against XDRs ===
+**Report template**
+--------
+### Code Review Against XDRs
 Scope: [scope identifier]
-Files Analyzed: [number]
-Changes: [+X lines, -Y lines]
 
-=== Findings ===
-[findings list]
+## Findings
+### 1. [ERROR|WARNING] - [filename:line_number](filename:line_number)
+- Title of the finding (<=15 words)
+- XDR reference: [xdr-file:line_number](xdr-file:line_number)
+- Why: Brief description of the issue in 20 words
+- Fix: Specific action to fix this issue in 15 words
+- Relevance: Why this matters / What to watch for in 15 words
 
-=== Summary ===
-- Errors Found: [count]
-- Warnings Found: [count]
-- Review Status: [PASS|FAIL]
+### 2. [second finding etc]
 
-Affected Files Requiring Changes
-[bullet list of files with markdown links to specific findings and severity]
-```
+## Summary
+- Errors: [count]
+- Warnings: [count]
+- Outcome: [PASS|FAIL]
+--------
 
 ### Constraints
-
 - MUST NOT include any text or explanations outside the required output format.
 - MUST NOT edit code. Instruct the user on how to request code changes in suggestions.
 
 ## Examples
-
-User: "Review my changes against XDRs"
-Agent action: runs `git diff origin/main`, reads `.xdrs/` hierarchy, filters applicable XDRs,
-produces structured findings report.
-
-User: "Lint the auth service"
-Agent action: scans all files under the auth service directory, applies relevant XDRs,
-produces structured findings report.
+- An XDR mentions that "Every code MUST have a header comment with author name", if you find a codebase without the author name, report as ERROR.
+- An XDR mentions that "Functions SHOULD be no longer than 50 lines", if you find a function with 80 lines, report as WARNING.
 
 ## Edge Cases
-
 - If no XDRs apply to the scope, output "No applicable XDRs found" and skip reporting.
-- If `git diff` fails (no git repo, no remote), fall back to analyzing staged or working tree files.
 - If a potential violation is in pre-existing code outside the diff, report it as WARNING only.
 
 ## References

package/.xdrs/index.md

@@ -11,15 +11,9 @@ XDRs in scopes listed last override the ones listed first
 Decisions about how XDRs work
 [View general ADRs Index](_core/adrs/index.md)
 
-Decisions about how XDRs work
-[View general EDRs Index](_core/edrs/index.md)
-
 ---
 
-### agentkit
-
-General engineering decisions from agentkit scope
-[View agentkit EDRs Index](agentkit/edrs/index.md)
+[OTHER SCOPES HERE]
 
 ---
 

package/AGENTS.md

@@ -2,18 +2,20 @@
 
 **Purpose:** This file is intentionally brief. All project decisions and working instructions are captured as XDRs.
 
-1. **Always consult XDRs before making implementation decisions**
-   - You MUST follow coding agent behavior and decision hierarchy rules in [.xdrs/_core/edrs/principles/001-coding-agent-behavior.md](.xdrs/_core/edrs/principles/001-coding-agent-behavior.md)
-   - You MUST search and follow XDRs in [.xdrs/index.md](.xdrs/index.md) during design, plan, implementation, test and review steps
-   - You MUST follow XDRs as the source of truth for all decisions and procedures
+1. **Always consult XDRs before making decisions**
+   - You MUST search and follow Decision Records (XDRs) for architecture, engineering and business in [.xdrs/index.md](.xdrs/index.md) during design, plan, implementation, test and review steps. This is the source of truth.
 
 2. **Verify all work with build, tests and linting before completion**
-   - Always run `make build`, `make lint-fix` and `make test` at the end of the implementation
+   - Always run build, lint-fix and test at the end of the implementation
    - Fix any issues
 
 3. **Verify if implementation complies with XDRs**
-   - Re-analyse your work against the XDRs and ensure implementation decisions follow guidelines and patterns
+   - Analyse your work against the XDRs and ensure implementation decisions follow guidelines and patterns
+   - Fix any issues
+
+4. **Do not perform git operations unless explicitelly asked**
+   - The developer should be in control of possible destructive operations on the workspace
 
-4. **Do not perform git operations**
-   - Do not run git commands (add, commit, push, branch creation, etc.)
+Check for additional instructions on [AGENTS-LOCAL.md](AGENTS-LOCAL.md).
 
+**This AGENTS.md file was created with xdrs-core and shouldn't be changed**

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "xdrs-core",
-  "version": "0.2.15",
+  "version": "0.2.16",
   "description": "A standard way to organize Decision Records (XDRs) across scopes, subjects, and teams so that AI agents can reliably query and follow them.",
   "repository": {
     "type": "git",
@@ -20,35 +20,45 @@
     "bin/npmdata.js"
   ],
   "dependencies": {
-    "npmdata": "^0.14.0"
+    "npmdata": "^0.15.1"
   },
   "npmdata": {
     "sets": [
       {
         "package": "xdrs-core",
-        "outputDir": ".",
-        "files": [
-          "AGENTS.md",
-          ".xdrs/**",
-          "!.xdrs/index.md"
-        ],
-        "symlinks": [
-          {
-            "source": ".xdrs/**/skills/*",
-            "target": "./.github/skills"
-          }
-        ],
-        "gitignore": false
+        "selector": {
+          "files": [
+            "AGENTS.md",
+            ".xdrs/**"
+          ],
+          "exclude": [
+            ".xdrs/index.md"
+          ]
+        },
+        "output": {
+          "path": ".",
+          "symlinks": [
+            {
+              "source": ".xdrs/**/skills/*",
+              "target": ".github/skills"
+            }
+          ],
+          "gitignore": false
+        }
       },
       {
         "package": "xdrs-core",
-        "outputDir": ".",
-        "files": [
-          ".xdrs/index.md"
-        ],
-        "gitignore": false,
-        "unmanaged": true,
-        "keepExisting": true
+        "selector": {
+          "files": [
+            ".xdrs/index.md"
+          ]
+        },
+        "output": {
+          "path": ".",
+          "gitignore": false,
+          "unmanaged": true,
+          "keepExisting": true
+        }
       }
     ]
   },

package/.xdrs/_core/edrs/index.md

@@ -1,10 +0,0 @@
-# general EDRs Index
-
-General engineering decisions covering cross-business standards and practices. Applies to all AI coding agents working in any scope. Owned by the platform team. Propose changes via pull request.
-
-## Principles
-
-Foundational standards, principles, and guidelines.
-
-- [_core-edr-001](principles/001-coding-agent-behavior.md) - **AI coding agent behavior**
-

package/.xdrs/_core/edrs/principles/001-coding-agent-behavior.md

@@ -1,37 +0,0 @@
-# _core-edr-001: AI coding agent behavior
-
-## Context and Problem Statement
-
-AI coding agents (such as GitHub Copilot) require clear guidelines about expected behavior to ensure consistency, proper verification of work, and respect for developer workflows.
-
-What behavioral standards should AI coding agents follow when working on code?
-
-## Decision Outcome
-
-**AI agents must follow a defined instruction hierarchy, verify work with automated checks, and defer git operations to developers**
-
-Clear behavior standards ensure consistency through EDR compliance, maintain code quality through automated verification, and respect the developer's role in version control decisions.
-
-### Implementation Details
-
-**Mandatory behaviors for AI coding agents:**
-
-1. **Always consult XDRs before making implementation decisions**
-   - Follow coding agent behavior and decision hierarchy rules in [.xdrs/_core/edrs/principles/001-coding-agent-behavior.md](.xdrs/_core/edrs/principles/001-coding-agent-behavior.md)
-   - Search for XDRs in [.xdrs/index.md](.xdrs/index.md) during design, plan and implementation steps
-   - Follow XDRs as the source of truth for all decisions and procedures
-
-2. **Verify all work with build, tests and linting before completion**
-   - Always run `make build`, `make lint-fix` and `make test` at the end of the implementation
-   - Fix any issues
-
-3. **Verify if implementation complies with XDRs**
-   - Re-analyse your work against the XDRs and ensure implementation decisions follow guidelines and patterns
-
-
-## Considered Options
-
-* (REJECTED) **Minimal guidance** - Let agents operate with default behavior
-  * Reason: Results in inconsistent code quality, missed verification steps, and developers losing control of git workflow
-* (CHOSEN) **EDR-compliant agents** - Clear behavior standards
-  * Reason: Ensures consistency through EDR compliance, maintains code quality through verification, and respects developer control of version control