xdrs-core 0.2.10-beta.0 → 0.2.13

package/.xdrs/_general/adrs/principles/skills/001-xdr-lint/SKILL.md

@@ -16,53 +16,46 @@ categorizing findings by severity and type, and reporting them without modifying
 
 ## Instructions
 
-### Phase 1: XDR Compilation
+### Phase 1: Code Gathering
+
+1. Identify changes based on requested scope:
+   - For diffs: run and parse `git diff origin/main`
+   - For files: analyze file contents directly
+
+### Phase 2: XDR Compilation
 
 1. Gather all Decision Records from `.xdrs/index.md` starting from the working directory.
    - XDR scopes are controlled by nested folders; some are broad, others domain-specific.
    - Extract metadata first (status, impact, scope, applicability) to filter relevant XDRs before deep analysis.
 2. Filter relevance based on file types, domains, and architectural patterns in scope.
 
-### Phase 2: Code Analysis
+### Phase 3: XDR Review
 
-1. Identify changes based on requested scope:
-   - For diffs: run and parse `git diff origin/main`
-   - For files: analyze file contents directly
-   - For services: scan all files in the service directory
-2. Categorize potential findings:
-   - Architecture: violations of structural decisions
-   - Coding Standards: style and pattern violations
-   - Testing: missing or inadequate test coverage
-   - Documentation: missing or outdated documentation
-   - Security: security practice violations
-   - Performance: performance best practice violations
-3. Compile specific, measurable rules from each XDR and compare against the changes.
-4. Prioritize by criticality: Accepted > Proposed; Impact: critical > high > medium > low.
-
-### Phase 3: Review and Judgment
-
-1. Cross-reference each finding against applicable XDRs.
+1. Cross-reference each file in scope against applicable XDRs.
    - **Drop any finding that cannot be traced to a specific rule in an Accepted XDR.** General good-practice observations, personal opinions, or inferred issues without an explicit XDR backing must not be reported.
    - Classify as ERROR (mandatory) or WARNING (advisory).
    - Include: location, description, XDR reference (file + line), suggestion.
 2. Reduce false positives:
-   - Re-evaluate ERROR findings for mandatory language in the XDR ("must", "always", "never", "required", "mandatory"). Drop or downgrade to WARNING if the language is advisory ("should", "recommended", "advised").
+   - Evaluate ERROR findings for mandatory language in the XDR ("must", "always", "never", "required", "mandatory"). Drop or downgrade to WARNING if the language is advisory ("should", "recommended", "advised").
    - Remove findings unrelated to actual changes.
    - Consolidate duplicates.
    - Consider context (existing style, legacy sections, etc.).
+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):
-   - Is the violation explicitly stated in an Accepted XDR? (If no, drop it.)
+   - 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?
    - Would fixing it meaningfully improve compliance with the XDR?
 
-### Phase 4: Reporting
+### Phase 5: Reporting
 
 Format each finding as:
 
 ```
->> [ERROR|WARNING] [CATEGORY] filename:line_number: Description
-   - XDR Reference: .xdrs/scope/type/subject/number-title.md:line_number
+>> [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
@@ -86,7 +79,7 @@ Changes: [+X lines, -Y lines]
 - Review Status: [PASS|FAIL]
 
 Affected Files Requiring Changes
-[bullet list of files with issues, linked to specific findings and severity]
+[bullet list of files with markdown links to specific findings and severity]
 ```
 
 ### Constraints

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

@@ -16,23 +16,18 @@ Clear behavior standards ensure consistency through EDR compliance, maintain cod
 
 **Mandatory behaviors for AI coding agents:**
 
-1. **Follow instruction hierarchy when making implementation decisions**
-   1. **Closest AGENTS.md** to the file being changed (search from target directory up to workspace root). Instructions in those files override the global EDRs. If multiple AGENTS.md files exist in the path, merge their instructions; the closest AGENTS.md overrides those farther away.
-   2. **Global EDR** – Follow scope-based precedence defined in [.xdrs/index.md](../../../../index.md). EDRs in scopes listed last override EDRs in scopes listed first.
+1. **Always consult XDRs before making implementation decisions**
+   - Follow coding agent behavior and decision hierarchy rules in [.xdrs/_general/edrs/principles/001-coding-agent-behavior.md](.xdrs/_general/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**
-   - Check EDRs for workspace tooling: [.xdrs/index.md](../../../../index.md)
-   - Run quality checks in sequence relative to the module directory: `STAGE=dev make build-module`, `make lint-module`, then `make test-module`
-   - Use `make lint-fix` to fix lint issues
-   - Do not run commands outside Makefiles
-
-3. **Verify implementation complies with EDRs**
-   - Review relevant EDRs before marking work complete
-   - Ensure implementation decisions follow EDR guidelines and patterns
-
-4. **Do not perform git operations**
-   - Do not run git commands (add, commit, push, branch creation, etc.)
-   - Inform the developer when work is ready for version control
+   - 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
 

package/.xdrs/index.md

@@ -20,6 +20,14 @@ General engineering decisions covering cross-business standards and practices.
 
 ---
 
+### EDRs - agentkit
+
+General engineering decisions from agentkit scope
+
+[View agentkit EDRs Index](agentkit/edrs/index.md)
+
+---
+
 ### _local (reserved)
 
 Project-local XDRs that must not be shared with other contexts. Always keep this scope last so its decisions override or extend all scopes listed above. Add specific `_local` ADR/BDR/EDR index links here when present.

package/AGENTS.md

@@ -8,6 +8,7 @@
    - 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**

package/bin/npmdata.js

@@ -1,4 +1,3 @@
 #!/usr/bin/env node
-
-// DON'T EDIT THIS FILE MANUALLY - this script is generated by "npmdata init" command
-require('npmdata/dist/runner.js').run(__dirname);
+'use strict';
+require('npmdata').binpkg(__dirname, process.argv.slice(2));

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "xdrs-core",
-  "version": "0.2.10-beta.0",
+  "version": "0.2.13",
   "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,7 +20,7 @@
     "bin/npmdata.js"
   ],
   "dependencies": {
-    "npmdata": "^0.11.0"
+    "npmdata": "^0.13.3"
   },
   "npmdata": {
     "sets": [