compose-agentsmd 3.2.0 → 3.2.1

package/README.md

@@ -33,6 +33,7 @@ compose-agentsmd
 The tool reads `agent-ruleset.json` from the given root directory (default: current working directory), and writes the output file specified by the ruleset. If `output` is omitted, it defaults to `AGENTS.md`.
 
 The tool prepends a small "Tool Rules" block to every generated `AGENTS.md` so agents know how to regenerate or update rules.
+Each composed rule section is also prefixed with the source file path that produced it.
 
 ## Setup (init)
 

package/dist/compose-agents.js

@@ -527,7 +527,10 @@ const composeRuleset = (rulesetPath, rootDir, options) => {
     const extraRules = Array.isArray(projectRuleset.extra) ? projectRuleset.extra : [];
     const directRulePaths = extraRules.map((rulePath) => resolveFrom(rulesetDir, rulePath));
     addRulePaths(directRulePaths, resolvedRules, seenRules);
-    const parts = resolvedRules.map((rulePath) => normalizeTrailingWhitespace(fs.readFileSync(rulePath, "utf8")));
+    const parts = resolvedRules.map((rulePath) => {
+        const body = normalizeTrailingWhitespace(fs.readFileSync(rulePath, "utf8"));
+        return `Source: ${normalizePath(rulePath)}\n\n${body}`;
+    });
     const lintHeader = "<!-- markdownlint-disable MD025 -->";
     const toolRules = normalizeTrailingWhitespace(TOOL_RULES);
     const output = `${lintHeader}\n${[toolRules, ...parts].join("\n\n")}\n`;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "compose-agentsmd",
-  "version": "3.2.0",
+  "version": "3.2.1",
   "description": "CLI tools for composing per-project AGENTS.md files from modular rule sets",
   "license": "MIT",
   "repository": {

package/tools/tool-rules.md

@@ -2,4 +2,6 @@
 - Before starting any work, run `compose-agentsmd` from the project root.
 - To update shared rules, run `compose-agentsmd edit-rules`, edit the workspace rules, then run `compose-agentsmd apply-rules`.
 - Do not edit `AGENTS.md` directly; update the source rules and regenerate.
-- When updating rules, include a detailed summary of what changed (added/removed/modified items) in the final response.
+- When updating rules, include a colorized diff-style summary in the final response. Use `git diff --stat` first, then include the raw ANSI-colored output of `git diff --color=always` (no sanitizing or reformatting), and limit the output to the rule files that changed.
+- Also provide a short, copy-pasteable command the user can run to view the diff in the same format. Use absolute paths so it works regardless of the current working directory, and scope it to the changed rule files.
+- If a diff is provided, a separate detailed summary is not required. If a diff is not possible, include a detailed summary of what changed (added/removed/modified items).