diff --git a/graphify/skill-agents.md b/graphify/skill-agents.md index 435bd1fed..ab62ce0fc 100644 --- a/graphify/skill-agents.md +++ b/graphify/skill-agents.md @@ -648,6 +648,8 @@ If graphify saved you time, consider supporting it: https://github.com/sponsors/ Replace PATH_TO_DIR with the actual absolute path of the directory that was processed. +If PATH_TO_DIR is inside a git repository, add one line to the report: `graphify-out/` was written into the working tree, so unless the repository already ignores it, it will show in `git status`; the user can add `graphify-out/` to `.gitignore`, or commit only the outputs their team should share (see https://docs.graphify.com/guides/team-workflows). + Then paste these sections from GRAPH_REPORT.md directly into the chat: - God Nodes - Surprising Connections diff --git a/graphify/skill-aider.md b/graphify/skill-aider.md index 2ca7f3bf2..c3c6b9f70 100644 --- a/graphify/skill-aider.md +++ b/graphify/skill-aider.md @@ -747,6 +747,8 @@ If graphify saved you time, consider supporting it: https://github.com/sponsors/ Replace PATH_TO_DIR with the actual absolute path of the directory that was processed. +If PATH_TO_DIR is inside a git repository, add one line to the report: `graphify-out/` was written into the working tree, so unless the repository already ignores it, it will show in `git status`; the user can add `graphify-out/` to `.gitignore`, or commit only the outputs their team should share (see https://docs.graphify.com/guides/team-workflows). + Then paste these sections from GRAPH_REPORT.md directly into the chat: - God Nodes - Surprising Connections diff --git a/graphify/skill-amp.md b/graphify/skill-amp.md index 435bd1fed..ab62ce0fc 100644 --- a/graphify/skill-amp.md +++ b/graphify/skill-amp.md @@ -648,6 +648,8 @@ If graphify saved you time, consider supporting it: https://github.com/sponsors/ Replace PATH_TO_DIR with the actual absolute path of the directory that was processed. +If PATH_TO_DIR is inside a git repository, add one line to the report: `graphify-out/` was written into the working tree, so unless the repository already ignores it, it will show in `git status`; the user can add `graphify-out/` to `.gitignore`, or commit only the outputs their team should share (see https://docs.graphify.com/guides/team-workflows). + Then paste these sections from GRAPH_REPORT.md directly into the chat: - God Nodes - Surprising Connections diff --git a/graphify/skill-claw.md b/graphify/skill-claw.md index 4611240c5..f987d759a 100644 --- a/graphify/skill-claw.md +++ b/graphify/skill-claw.md @@ -651,6 +651,8 @@ If graphify saved you time, consider supporting it: https://github.com/sponsors/ Replace PATH_TO_DIR with the actual absolute path of the directory that was processed. +If PATH_TO_DIR is inside a git repository, add one line to the report: `graphify-out/` was written into the working tree, so unless the repository already ignores it, it will show in `git status`; the user can add `graphify-out/` to `.gitignore`, or commit only the outputs their team should share (see https://docs.graphify.com/guides/team-workflows). + Then paste these sections from GRAPH_REPORT.md directly into the chat: - God Nodes - Surprising Connections diff --git a/graphify/skill-codex.md b/graphify/skill-codex.md index 952f319b1..93746d73a 100644 --- a/graphify/skill-codex.md +++ b/graphify/skill-codex.md @@ -648,6 +648,8 @@ If graphify saved you time, consider supporting it: https://github.com/sponsors/ Replace PATH_TO_DIR with the actual absolute path of the directory that was processed. +If PATH_TO_DIR is inside a git repository, add one line to the report: `graphify-out/` was written into the working tree, so unless the repository already ignores it, it will show in `git status`; the user can add `graphify-out/` to `.gitignore`, or commit only the outputs their team should share (see https://docs.graphify.com/guides/team-workflows). + Then paste these sections from GRAPH_REPORT.md directly into the chat: - God Nodes - Surprising Connections diff --git a/graphify/skill-copilot.md b/graphify/skill-copilot.md index 4611240c5..f987d759a 100644 --- a/graphify/skill-copilot.md +++ b/graphify/skill-copilot.md @@ -651,6 +651,8 @@ If graphify saved you time, consider supporting it: https://github.com/sponsors/ Replace PATH_TO_DIR with the actual absolute path of the directory that was processed. +If PATH_TO_DIR is inside a git repository, add one line to the report: `graphify-out/` was written into the working tree, so unless the repository already ignores it, it will show in `git status`; the user can add `graphify-out/` to `.gitignore`, or commit only the outputs their team should share (see https://docs.graphify.com/guides/team-workflows). + Then paste these sections from GRAPH_REPORT.md directly into the chat: - God Nodes - Surprising Connections diff --git a/graphify/skill-devin.md b/graphify/skill-devin.md index b9be67de9..bc9dfa04e 100644 --- a/graphify/skill-devin.md +++ b/graphify/skill-devin.md @@ -866,6 +866,8 @@ If graphify saved you time, consider supporting it: https://github.com/sponsors/ Replace PATH_TO_DIR with the actual absolute path of the directory that was processed. +If PATH_TO_DIR is inside a git repository, add one line to the report: `graphify-out/` was written into the working tree, so unless the repository already ignores it, it will show in `git status`; the user can add `graphify-out/` to `.gitignore`, or commit only the outputs their team should share (see https://docs.graphify.com/guides/team-workflows). + Then paste these sections from GRAPH_REPORT.md directly into the chat: - God Nodes - Surprising Connections diff --git a/graphify/skill-droid.md b/graphify/skill-droid.md index 91767d3c3..41b368a4e 100644 --- a/graphify/skill-droid.md +++ b/graphify/skill-droid.md @@ -648,6 +648,8 @@ If graphify saved you time, consider supporting it: https://github.com/sponsors/ Replace PATH_TO_DIR with the actual absolute path of the directory that was processed. +If PATH_TO_DIR is inside a git repository, add one line to the report: `graphify-out/` was written into the working tree, so unless the repository already ignores it, it will show in `git status`; the user can add `graphify-out/` to `.gitignore`, or commit only the outputs their team should share (see https://docs.graphify.com/guides/team-workflows). + Then paste these sections from GRAPH_REPORT.md directly into the chat: - God Nodes - Surprising Connections diff --git a/graphify/skill-kilo.md b/graphify/skill-kilo.md index 73eb3ef61..7c0555124 100644 --- a/graphify/skill-kilo.md +++ b/graphify/skill-kilo.md @@ -651,6 +651,8 @@ If graphify saved you time, consider supporting it: https://github.com/sponsors/ Replace PATH_TO_DIR with the actual absolute path of the directory that was processed. +If PATH_TO_DIR is inside a git repository, add one line to the report: `graphify-out/` was written into the working tree, so unless the repository already ignores it, it will show in `git status`; the user can add `graphify-out/` to `.gitignore`, or commit only the outputs their team should share (see https://docs.graphify.com/guides/team-workflows). + Then paste these sections from GRAPH_REPORT.md directly into the chat: - God Nodes - Surprising Connections diff --git a/graphify/skill-kiro.md b/graphify/skill-kiro.md index 4611240c5..f987d759a 100644 --- a/graphify/skill-kiro.md +++ b/graphify/skill-kiro.md @@ -651,6 +651,8 @@ If graphify saved you time, consider supporting it: https://github.com/sponsors/ Replace PATH_TO_DIR with the actual absolute path of the directory that was processed. +If PATH_TO_DIR is inside a git repository, add one line to the report: `graphify-out/` was written into the working tree, so unless the repository already ignores it, it will show in `git status`; the user can add `graphify-out/` to `.gitignore`, or commit only the outputs their team should share (see https://docs.graphify.com/guides/team-workflows). + Then paste these sections from GRAPH_REPORT.md directly into the chat: - God Nodes - Surprising Connections diff --git a/graphify/skill-opencode.md b/graphify/skill-opencode.md index aeba6b0df..07deeecc1 100644 --- a/graphify/skill-opencode.md +++ b/graphify/skill-opencode.md @@ -643,6 +643,8 @@ If graphify saved you time, consider supporting it: https://github.com/sponsors/ Replace PATH_TO_DIR with the actual absolute path of the directory that was processed. +If PATH_TO_DIR is inside a git repository, add one line to the report: `graphify-out/` was written into the working tree, so unless the repository already ignores it, it will show in `git status`; the user can add `graphify-out/` to `.gitignore`, or commit only the outputs their team should share (see https://docs.graphify.com/guides/team-workflows). + Then paste these sections from GRAPH_REPORT.md directly into the chat: - God Nodes - Surprising Connections diff --git a/graphify/skill-pi.md b/graphify/skill-pi.md index 4611240c5..f987d759a 100644 --- a/graphify/skill-pi.md +++ b/graphify/skill-pi.md @@ -651,6 +651,8 @@ If graphify saved you time, consider supporting it: https://github.com/sponsors/ Replace PATH_TO_DIR with the actual absolute path of the directory that was processed. +If PATH_TO_DIR is inside a git repository, add one line to the report: `graphify-out/` was written into the working tree, so unless the repository already ignores it, it will show in `git status`; the user can add `graphify-out/` to `.gitignore`, or commit only the outputs their team should share (see https://docs.graphify.com/guides/team-workflows). + Then paste these sections from GRAPH_REPORT.md directly into the chat: - God Nodes - Surprising Connections diff --git a/graphify/skill-trae.md b/graphify/skill-trae.md index a5878899d..f58780d17 100644 --- a/graphify/skill-trae.md +++ b/graphify/skill-trae.md @@ -649,6 +649,8 @@ If graphify saved you time, consider supporting it: https://github.com/sponsors/ Replace PATH_TO_DIR with the actual absolute path of the directory that was processed. +If PATH_TO_DIR is inside a git repository, add one line to the report: `graphify-out/` was written into the working tree, so unless the repository already ignores it, it will show in `git status`; the user can add `graphify-out/` to `.gitignore`, or commit only the outputs their team should share (see https://docs.graphify.com/guides/team-workflows). + Then paste these sections from GRAPH_REPORT.md directly into the chat: - God Nodes - Surprising Connections diff --git a/graphify/skill-vscode.md b/graphify/skill-vscode.md index c3d571d86..adac00415 100644 --- a/graphify/skill-vscode.md +++ b/graphify/skill-vscode.md @@ -647,6 +647,8 @@ If graphify saved you time, consider supporting it: https://github.com/sponsors/ Replace PATH_TO_DIR with the actual absolute path of the directory that was processed. +If PATH_TO_DIR is inside a git repository, add one line to the report: `graphify-out/` was written into the working tree, so unless the repository already ignores it, it will show in `git status`; the user can add `graphify-out/` to `.gitignore`, or commit only the outputs their team should share (see https://docs.graphify.com/guides/team-workflows). + Then paste these sections from GRAPH_REPORT.md directly into the chat: - God Nodes - Surprising Connections diff --git a/graphify/skill-windows.md b/graphify/skill-windows.md index fc2f2ccfd..e1f775aff 100644 --- a/graphify/skill-windows.md +++ b/graphify/skill-windows.md @@ -679,6 +679,8 @@ If graphify saved you time, consider supporting it: https://github.com/sponsors/ Replace PATH_TO_DIR with the actual absolute path of the directory that was processed. +If PATH_TO_DIR is inside a git repository, add one line to the report: `graphify-out/` was written into the working tree, so unless the repository already ignores it, it will show in `git status`; the user can add `graphify-out/` to `.gitignore`, or commit only the outputs their team should share (see https://docs.graphify.com/guides/team-workflows). + Then paste these sections from GRAPH_REPORT.md directly into the chat: - God Nodes - Surprising Connections diff --git a/graphify/skill.md b/graphify/skill.md index 4611240c5..f987d759a 100644 --- a/graphify/skill.md +++ b/graphify/skill.md @@ -651,6 +651,8 @@ If graphify saved you time, consider supporting it: https://github.com/sponsors/ Replace PATH_TO_DIR with the actual absolute path of the directory that was processed. +If PATH_TO_DIR is inside a git repository, add one line to the report: `graphify-out/` was written into the working tree, so unless the repository already ignores it, it will show in `git status`; the user can add `graphify-out/` to `.gitignore`, or commit only the outputs their team should share (see https://docs.graphify.com/guides/team-workflows). + Then paste these sections from GRAPH_REPORT.md directly into the chat: - God Nodes - Surprising Connections diff --git a/tools/skillgen/expected/graphify__skill-agents.md b/tools/skillgen/expected/graphify__skill-agents.md index 435bd1fed..ab62ce0fc 100644 --- a/tools/skillgen/expected/graphify__skill-agents.md +++ b/tools/skillgen/expected/graphify__skill-agents.md @@ -648,6 +648,8 @@ If graphify saved you time, consider supporting it: https://github.com/sponsors/ Replace PATH_TO_DIR with the actual absolute path of the directory that was processed. +If PATH_TO_DIR is inside a git repository, add one line to the report: `graphify-out/` was written into the working tree, so unless the repository already ignores it, it will show in `git status`; the user can add `graphify-out/` to `.gitignore`, or commit only the outputs their team should share (see https://docs.graphify.com/guides/team-workflows). + Then paste these sections from GRAPH_REPORT.md directly into the chat: - God Nodes - Surprising Connections diff --git a/tools/skillgen/expected/graphify__skill-aider.md b/tools/skillgen/expected/graphify__skill-aider.md index 2ca7f3bf2..c3c6b9f70 100644 --- a/tools/skillgen/expected/graphify__skill-aider.md +++ b/tools/skillgen/expected/graphify__skill-aider.md @@ -747,6 +747,8 @@ If graphify saved you time, consider supporting it: https://github.com/sponsors/ Replace PATH_TO_DIR with the actual absolute path of the directory that was processed. +If PATH_TO_DIR is inside a git repository, add one line to the report: `graphify-out/` was written into the working tree, so unless the repository already ignores it, it will show in `git status`; the user can add `graphify-out/` to `.gitignore`, or commit only the outputs their team should share (see https://docs.graphify.com/guides/team-workflows). + Then paste these sections from GRAPH_REPORT.md directly into the chat: - God Nodes - Surprising Connections diff --git a/tools/skillgen/expected/graphify__skill-amp.md b/tools/skillgen/expected/graphify__skill-amp.md index 435bd1fed..ab62ce0fc 100644 --- a/tools/skillgen/expected/graphify__skill-amp.md +++ b/tools/skillgen/expected/graphify__skill-amp.md @@ -648,6 +648,8 @@ If graphify saved you time, consider supporting it: https://github.com/sponsors/ Replace PATH_TO_DIR with the actual absolute path of the directory that was processed. +If PATH_TO_DIR is inside a git repository, add one line to the report: `graphify-out/` was written into the working tree, so unless the repository already ignores it, it will show in `git status`; the user can add `graphify-out/` to `.gitignore`, or commit only the outputs their team should share (see https://docs.graphify.com/guides/team-workflows). + Then paste these sections from GRAPH_REPORT.md directly into the chat: - God Nodes - Surprising Connections diff --git a/tools/skillgen/expected/graphify__skill-claw.md b/tools/skillgen/expected/graphify__skill-claw.md index 4611240c5..f987d759a 100644 --- a/tools/skillgen/expected/graphify__skill-claw.md +++ b/tools/skillgen/expected/graphify__skill-claw.md @@ -651,6 +651,8 @@ If graphify saved you time, consider supporting it: https://github.com/sponsors/ Replace PATH_TO_DIR with the actual absolute path of the directory that was processed. +If PATH_TO_DIR is inside a git repository, add one line to the report: `graphify-out/` was written into the working tree, so unless the repository already ignores it, it will show in `git status`; the user can add `graphify-out/` to `.gitignore`, or commit only the outputs their team should share (see https://docs.graphify.com/guides/team-workflows). + Then paste these sections from GRAPH_REPORT.md directly into the chat: - God Nodes - Surprising Connections diff --git a/tools/skillgen/expected/graphify__skill-codex.md b/tools/skillgen/expected/graphify__skill-codex.md index 952f319b1..93746d73a 100644 --- a/tools/skillgen/expected/graphify__skill-codex.md +++ b/tools/skillgen/expected/graphify__skill-codex.md @@ -648,6 +648,8 @@ If graphify saved you time, consider supporting it: https://github.com/sponsors/ Replace PATH_TO_DIR with the actual absolute path of the directory that was processed. +If PATH_TO_DIR is inside a git repository, add one line to the report: `graphify-out/` was written into the working tree, so unless the repository already ignores it, it will show in `git status`; the user can add `graphify-out/` to `.gitignore`, or commit only the outputs their team should share (see https://docs.graphify.com/guides/team-workflows). + Then paste these sections from GRAPH_REPORT.md directly into the chat: - God Nodes - Surprising Connections diff --git a/tools/skillgen/expected/graphify__skill-copilot.md b/tools/skillgen/expected/graphify__skill-copilot.md index 4611240c5..f987d759a 100644 --- a/tools/skillgen/expected/graphify__skill-copilot.md +++ b/tools/skillgen/expected/graphify__skill-copilot.md @@ -651,6 +651,8 @@ If graphify saved you time, consider supporting it: https://github.com/sponsors/ Replace PATH_TO_DIR with the actual absolute path of the directory that was processed. +If PATH_TO_DIR is inside a git repository, add one line to the report: `graphify-out/` was written into the working tree, so unless the repository already ignores it, it will show in `git status`; the user can add `graphify-out/` to `.gitignore`, or commit only the outputs their team should share (see https://docs.graphify.com/guides/team-workflows). + Then paste these sections from GRAPH_REPORT.md directly into the chat: - God Nodes - Surprising Connections diff --git a/tools/skillgen/expected/graphify__skill-devin.md b/tools/skillgen/expected/graphify__skill-devin.md index b9be67de9..bc9dfa04e 100644 --- a/tools/skillgen/expected/graphify__skill-devin.md +++ b/tools/skillgen/expected/graphify__skill-devin.md @@ -866,6 +866,8 @@ If graphify saved you time, consider supporting it: https://github.com/sponsors/ Replace PATH_TO_DIR with the actual absolute path of the directory that was processed. +If PATH_TO_DIR is inside a git repository, add one line to the report: `graphify-out/` was written into the working tree, so unless the repository already ignores it, it will show in `git status`; the user can add `graphify-out/` to `.gitignore`, or commit only the outputs their team should share (see https://docs.graphify.com/guides/team-workflows). + Then paste these sections from GRAPH_REPORT.md directly into the chat: - God Nodes - Surprising Connections diff --git a/tools/skillgen/expected/graphify__skill-droid.md b/tools/skillgen/expected/graphify__skill-droid.md index 91767d3c3..41b368a4e 100644 --- a/tools/skillgen/expected/graphify__skill-droid.md +++ b/tools/skillgen/expected/graphify__skill-droid.md @@ -648,6 +648,8 @@ If graphify saved you time, consider supporting it: https://github.com/sponsors/ Replace PATH_TO_DIR with the actual absolute path of the directory that was processed. +If PATH_TO_DIR is inside a git repository, add one line to the report: `graphify-out/` was written into the working tree, so unless the repository already ignores it, it will show in `git status`; the user can add `graphify-out/` to `.gitignore`, or commit only the outputs their team should share (see https://docs.graphify.com/guides/team-workflows). + Then paste these sections from GRAPH_REPORT.md directly into the chat: - God Nodes - Surprising Connections diff --git a/tools/skillgen/expected/graphify__skill-kilo.md b/tools/skillgen/expected/graphify__skill-kilo.md index 73eb3ef61..7c0555124 100644 --- a/tools/skillgen/expected/graphify__skill-kilo.md +++ b/tools/skillgen/expected/graphify__skill-kilo.md @@ -651,6 +651,8 @@ If graphify saved you time, consider supporting it: https://github.com/sponsors/ Replace PATH_TO_DIR with the actual absolute path of the directory that was processed. +If PATH_TO_DIR is inside a git repository, add one line to the report: `graphify-out/` was written into the working tree, so unless the repository already ignores it, it will show in `git status`; the user can add `graphify-out/` to `.gitignore`, or commit only the outputs their team should share (see https://docs.graphify.com/guides/team-workflows). + Then paste these sections from GRAPH_REPORT.md directly into the chat: - God Nodes - Surprising Connections diff --git a/tools/skillgen/expected/graphify__skill-kiro.md b/tools/skillgen/expected/graphify__skill-kiro.md index 4611240c5..f987d759a 100644 --- a/tools/skillgen/expected/graphify__skill-kiro.md +++ b/tools/skillgen/expected/graphify__skill-kiro.md @@ -651,6 +651,8 @@ If graphify saved you time, consider supporting it: https://github.com/sponsors/ Replace PATH_TO_DIR with the actual absolute path of the directory that was processed. +If PATH_TO_DIR is inside a git repository, add one line to the report: `graphify-out/` was written into the working tree, so unless the repository already ignores it, it will show in `git status`; the user can add `graphify-out/` to `.gitignore`, or commit only the outputs their team should share (see https://docs.graphify.com/guides/team-workflows). + Then paste these sections from GRAPH_REPORT.md directly into the chat: - God Nodes - Surprising Connections diff --git a/tools/skillgen/expected/graphify__skill-opencode.md b/tools/skillgen/expected/graphify__skill-opencode.md index aeba6b0df..07deeecc1 100644 --- a/tools/skillgen/expected/graphify__skill-opencode.md +++ b/tools/skillgen/expected/graphify__skill-opencode.md @@ -643,6 +643,8 @@ If graphify saved you time, consider supporting it: https://github.com/sponsors/ Replace PATH_TO_DIR with the actual absolute path of the directory that was processed. +If PATH_TO_DIR is inside a git repository, add one line to the report: `graphify-out/` was written into the working tree, so unless the repository already ignores it, it will show in `git status`; the user can add `graphify-out/` to `.gitignore`, or commit only the outputs their team should share (see https://docs.graphify.com/guides/team-workflows). + Then paste these sections from GRAPH_REPORT.md directly into the chat: - God Nodes - Surprising Connections diff --git a/tools/skillgen/expected/graphify__skill-pi.md b/tools/skillgen/expected/graphify__skill-pi.md index 4611240c5..f987d759a 100644 --- a/tools/skillgen/expected/graphify__skill-pi.md +++ b/tools/skillgen/expected/graphify__skill-pi.md @@ -651,6 +651,8 @@ If graphify saved you time, consider supporting it: https://github.com/sponsors/ Replace PATH_TO_DIR with the actual absolute path of the directory that was processed. +If PATH_TO_DIR is inside a git repository, add one line to the report: `graphify-out/` was written into the working tree, so unless the repository already ignores it, it will show in `git status`; the user can add `graphify-out/` to `.gitignore`, or commit only the outputs their team should share (see https://docs.graphify.com/guides/team-workflows). + Then paste these sections from GRAPH_REPORT.md directly into the chat: - God Nodes - Surprising Connections diff --git a/tools/skillgen/expected/graphify__skill-trae.md b/tools/skillgen/expected/graphify__skill-trae.md index a5878899d..f58780d17 100644 --- a/tools/skillgen/expected/graphify__skill-trae.md +++ b/tools/skillgen/expected/graphify__skill-trae.md @@ -649,6 +649,8 @@ If graphify saved you time, consider supporting it: https://github.com/sponsors/ Replace PATH_TO_DIR with the actual absolute path of the directory that was processed. +If PATH_TO_DIR is inside a git repository, add one line to the report: `graphify-out/` was written into the working tree, so unless the repository already ignores it, it will show in `git status`; the user can add `graphify-out/` to `.gitignore`, or commit only the outputs their team should share (see https://docs.graphify.com/guides/team-workflows). + Then paste these sections from GRAPH_REPORT.md directly into the chat: - God Nodes - Surprising Connections diff --git a/tools/skillgen/expected/graphify__skill-vscode.md b/tools/skillgen/expected/graphify__skill-vscode.md index c3d571d86..adac00415 100644 --- a/tools/skillgen/expected/graphify__skill-vscode.md +++ b/tools/skillgen/expected/graphify__skill-vscode.md @@ -647,6 +647,8 @@ If graphify saved you time, consider supporting it: https://github.com/sponsors/ Replace PATH_TO_DIR with the actual absolute path of the directory that was processed. +If PATH_TO_DIR is inside a git repository, add one line to the report: `graphify-out/` was written into the working tree, so unless the repository already ignores it, it will show in `git status`; the user can add `graphify-out/` to `.gitignore`, or commit only the outputs their team should share (see https://docs.graphify.com/guides/team-workflows). + Then paste these sections from GRAPH_REPORT.md directly into the chat: - God Nodes - Surprising Connections diff --git a/tools/skillgen/expected/graphify__skill-windows.md b/tools/skillgen/expected/graphify__skill-windows.md index fc2f2ccfd..e1f775aff 100644 --- a/tools/skillgen/expected/graphify__skill-windows.md +++ b/tools/skillgen/expected/graphify__skill-windows.md @@ -679,6 +679,8 @@ If graphify saved you time, consider supporting it: https://github.com/sponsors/ Replace PATH_TO_DIR with the actual absolute path of the directory that was processed. +If PATH_TO_DIR is inside a git repository, add one line to the report: `graphify-out/` was written into the working tree, so unless the repository already ignores it, it will show in `git status`; the user can add `graphify-out/` to `.gitignore`, or commit only the outputs their team should share (see https://docs.graphify.com/guides/team-workflows). + Then paste these sections from GRAPH_REPORT.md directly into the chat: - God Nodes - Surprising Connections diff --git a/tools/skillgen/expected/graphify__skill.md b/tools/skillgen/expected/graphify__skill.md index 4611240c5..f987d759a 100644 --- a/tools/skillgen/expected/graphify__skill.md +++ b/tools/skillgen/expected/graphify__skill.md @@ -651,6 +651,8 @@ If graphify saved you time, consider supporting it: https://github.com/sponsors/ Replace PATH_TO_DIR with the actual absolute path of the directory that was processed. +If PATH_TO_DIR is inside a git repository, add one line to the report: `graphify-out/` was written into the working tree, so unless the repository already ignores it, it will show in `git status`; the user can add `graphify-out/` to `.gitignore`, or commit only the outputs their team should share (see https://docs.graphify.com/guides/team-workflows). + Then paste these sections from GRAPH_REPORT.md directly into the chat: - God Nodes - Surprising Connections diff --git a/tools/skillgen/fragments/core/aider.md b/tools/skillgen/fragments/core/aider.md index 2ca7f3bf2..c3c6b9f70 100644 --- a/tools/skillgen/fragments/core/aider.md +++ b/tools/skillgen/fragments/core/aider.md @@ -747,6 +747,8 @@ If graphify saved you time, consider supporting it: https://github.com/sponsors/ Replace PATH_TO_DIR with the actual absolute path of the directory that was processed. +If PATH_TO_DIR is inside a git repository, add one line to the report: `graphify-out/` was written into the working tree, so unless the repository already ignores it, it will show in `git status`; the user can add `graphify-out/` to `.gitignore`, or commit only the outputs their team should share (see https://docs.graphify.com/guides/team-workflows). + Then paste these sections from GRAPH_REPORT.md directly into the chat: - God Nodes - Surprising Connections diff --git a/tools/skillgen/fragments/core/core.md b/tools/skillgen/fragments/core/core.md index dedf3a7c2..213003eb1 100644 --- a/tools/skillgen/fragments/core/core.md +++ b/tools/skillgen/fragments/core/core.md @@ -580,6 +580,8 @@ If graphify saved you time, consider supporting it: https://github.com/sponsors/ Replace PATH_TO_DIR with the actual absolute path of the directory that was processed. +If PATH_TO_DIR is inside a git repository, add one line to the report: `graphify-out/` was written into the working tree, so unless the repository already ignores it, it will show in `git status`; the user can add `graphify-out/` to `.gitignore`, or commit only the outputs their team should share (see https://docs.graphify.com/guides/team-workflows). + Then paste these sections from GRAPH_REPORT.md directly into the chat: - God Nodes - Surprising Connections diff --git a/tools/skillgen/fragments/core/devin.md b/tools/skillgen/fragments/core/devin.md index b9be67de9..bc9dfa04e 100644 --- a/tools/skillgen/fragments/core/devin.md +++ b/tools/skillgen/fragments/core/devin.md @@ -866,6 +866,8 @@ If graphify saved you time, consider supporting it: https://github.com/sponsors/ Replace PATH_TO_DIR with the actual absolute path of the directory that was processed. +If PATH_TO_DIR is inside a git repository, add one line to the report: `graphify-out/` was written into the working tree, so unless the repository already ignores it, it will show in `git status`; the user can add `graphify-out/` to `.gitignore`, or commit only the outputs their team should share (see https://docs.graphify.com/guides/team-workflows). + Then paste these sections from GRAPH_REPORT.md directly into the chat: - God Nodes - Surprising Connections diff --git a/tools/skillgen/gen.py b/tools/skillgen/gen.py index 993d0f2fe..d3fa13459 100644 --- a/tools/skillgen/gen.py +++ b/tools/skillgen/gen.py @@ -1209,6 +1209,17 @@ def _is_persisted_scan_options_fix_line(line: str) -> bool: ) +def _is_worktree_visibility_note_line(line: str) -> bool: + """Whether a line is the Step 9 working-tree note (#3941). + + Step 9's report never told the user that ``graphify-out/`` was written into + their working tree, so a repository that does not ignore it was left with + untracked machine-local files in ``git status`` and no explanation. The report + now adds one sentence saying so, with the two ways to handle it. + """ + return "`graphify-out/` was written into the working tree" in line + + # Every line that may differ between a rendered monolith and its pristine v8 # baseline. Each predicate documents one sanctioned change-class; a blank line is # allowed because the multi-line fix blocks insert spacing. Anything else failing @@ -1234,6 +1245,7 @@ _SANCTIONED_MONOLITH_DIFFS = ( _is_watch_injection_fix_line, _is_graph_diff_direction_fix_line, _is_persisted_scan_options_fix_line, + _is_worktree_visibility_note_line, )