From 18cc2cebd227085ee86433a020dfd64544e4e087 Mon Sep 17 00:00:00 2001 From: Orual Date: Fri, 24 Apr 2026 10:53:53 -0400 Subject: [PATCH] further implementation agent adjustments --- plugins/orual-plan-and-execute-popup/agents/task-bug-fixer.md | 2 +- .../agents/task-implementor-fast.md | 2 +- .../agents/task-implementor-heavy.md | 2 +- plugins/orual-plan-and-execute-popup/agents/task-implementor.md | 2 +- plugins/orual-plan-and-execute/agents/task-bug-fixer.md | 2 +- plugins/orual-plan-and-execute/agents/task-implementor-fast.md | 2 +- plugins/orual-plan-and-execute/agents/task-implementor-heavy.md | 2 +- plugins/orual-plan-and-execute/agents/task-implementor.md | 2 +- 8 files changed, 8 insertions(+), 8 deletions(-) diff --git a/plugins/orual-plan-and-execute-popup/agents/task-bug-fixer.md b/plugins/orual-plan-and-execute-popup/agents/task-bug-fixer.md index 56de3e8..2aee85e 100644 --- a/plugins/orual-plan-and-execute-popup/agents/task-bug-fixer.md +++ b/plugins/orual-plan-and-execute-popup/agents/task-bug-fixer.md @@ -49,7 +49,7 @@ For each issue: make the fix, verify it works, check for regressions. Run tests, build, linter. Everything must pass. Include evidence. -**Check your own changes with `jj diff` (or `git diff`).** This shows what YOU changed in the current session. If you edited a file and then grep the file to check whether an issue exists, you'll see your own fix and may falsely conclude the issue was "already fixed." Always check the VCS diff to know what you actually changed vs what was already there. +**Check your own changes with `jj diff` (or `git diff`).** This shows what YOU changed in the current session. When using git, check the VCS diff to know what you actually changed vs what was already there. When using jj, edits are automatically tracked, so the current change will show your edits. compare against a previous commit if uncertain. ### 5. Commit diff --git a/plugins/orual-plan-and-execute-popup/agents/task-implementor-fast.md b/plugins/orual-plan-and-execute-popup/agents/task-implementor-fast.md index e387461..52eddcb 100644 --- a/plugins/orual-plan-and-execute-popup/agents/task-implementor-fast.md +++ b/plugins/orual-plan-and-execute-popup/agents/task-implementor-fast.md @@ -57,7 +57,7 @@ npm run lint / cargo clippy / etc. If anything fails, fix it. Re-run until clean. Include evidence in your report. -**Check your own changes with `jj diff` (or `git diff`).** This shows what YOU changed in the current session. If you edited a file and then grep the file to check whether a change was applied, you'll see your own edit and may falsely conclude it was "already there." Always check the VCS diff to know what you actually changed vs what was already there. +**Check your own changes with `jj diff` (or `git diff`).** This shows what YOU changed in the current session. When using git, check the VCS diff to know what you actually changed vs what was already there. When using jj, edits are automatically tracked, so the current change will show your edits. compare against a previous commit if uncertain. ### 5. Commit diff --git a/plugins/orual-plan-and-execute-popup/agents/task-implementor-heavy.md b/plugins/orual-plan-and-execute-popup/agents/task-implementor-heavy.md index d446681..3f2d765 100644 --- a/plugins/orual-plan-and-execute-popup/agents/task-implementor-heavy.md +++ b/plugins/orual-plan-and-execute-popup/agents/task-implementor-heavy.md @@ -58,7 +58,7 @@ npm run lint / cargo clippy / etc. If anything fails, fix it. Re-run until clean. Include evidence in your report. -**Check your own changes with `jj diff` (or `git diff`).** This shows what YOU changed in the current session. If you edited a file and then grep the file to check whether a change was applied, you'll see your own edit and may falsely conclude it was "already there." Always check the VCS diff to know what you actually changed vs what was already there. +**Check your own changes with `jj diff` (or `git diff`).** This shows what YOU changed in the current session. When using git, check the VCS diff to know what you actually changed vs what was already there. When using jj, edits are automatically tracked, so the current change will show your edits. compare against a previous commit if uncertain. ### 5. Commit diff --git a/plugins/orual-plan-and-execute-popup/agents/task-implementor.md b/plugins/orual-plan-and-execute-popup/agents/task-implementor.md index 85350f3..01497e6 100644 --- a/plugins/orual-plan-and-execute-popup/agents/task-implementor.md +++ b/plugins/orual-plan-and-execute-popup/agents/task-implementor.md @@ -57,7 +57,7 @@ npm run lint / cargo clippy / etc. If anything fails, fix it. Re-run until clean. Include evidence in your report. -**Check your own changes with `jj diff` (or `git diff`).** This shows what YOU changed in the current session. If you edited a file and then grep the file to check whether a change was applied, you'll see your own edit and may falsely conclude it was "already there." Always check the VCS diff to know what you actually changed vs what was already there. +**Check your own changes with `jj diff` (or `git diff`).** This shows what YOU changed in the current session. When using git, check the VCS diff to know what you actually changed vs what was already there. When using jj, edits are automatically tracked, so the current change will show your edits. compare against a previous commit if uncertain. ### 5. Commit diff --git a/plugins/orual-plan-and-execute/agents/task-bug-fixer.md b/plugins/orual-plan-and-execute/agents/task-bug-fixer.md index ecb4aac..dd4c681 100644 --- a/plugins/orual-plan-and-execute/agents/task-bug-fixer.md +++ b/plugins/orual-plan-and-execute/agents/task-bug-fixer.md @@ -49,7 +49,7 @@ For each issue: make the fix, verify it works, check for regressions. Run tests, build, linter. Everything must pass. Include evidence. -**Check your own changes with `jj diff` (or `git diff`).** This shows what YOU changed in the current session. If you edited a file and then grep the file to check whether an issue exists, you'll see your own fix and may falsely conclude the issue was "already fixed." Always check the VCS diff to know what you actually changed vs what was already there. +**Check your own changes with `jj diff` (or `git diff`).** This shows what YOU changed in the current session. When using git, check the VCS diff to know what you actually changed vs what was already there. When using jj, edits are automatically tracked, so the current change will show your edits. compare against a previous commit if uncertain. ### 5. Commit diff --git a/plugins/orual-plan-and-execute/agents/task-implementor-fast.md b/plugins/orual-plan-and-execute/agents/task-implementor-fast.md index 9d3d14e..267cae0 100644 --- a/plugins/orual-plan-and-execute/agents/task-implementor-fast.md +++ b/plugins/orual-plan-and-execute/agents/task-implementor-fast.md @@ -57,7 +57,7 @@ npm run lint / cargo clippy / etc. If anything fails, fix it. Re-run until clean. Include evidence in your report. -**Check your own changes with `jj diff` (or `git diff`).** This shows what YOU changed in the current session. If you edited a file and then grep the file to check whether a change was applied, you'll see your own edit and may falsely conclude it was "already there." Always check the VCS diff to know what you actually changed vs what was already there. +**Check your own changes with `jj diff` (or `git diff`).** This shows what YOU changed in the current session. When using git, check the VCS diff to know what you actually changed vs what was already there. When using jj, edits are automatically tracked, so the current change will show your edits. compare against a previous commit if uncertain. ### 5. Commit diff --git a/plugins/orual-plan-and-execute/agents/task-implementor-heavy.md b/plugins/orual-plan-and-execute/agents/task-implementor-heavy.md index 132d44f..eeea468 100644 --- a/plugins/orual-plan-and-execute/agents/task-implementor-heavy.md +++ b/plugins/orual-plan-and-execute/agents/task-implementor-heavy.md @@ -58,7 +58,7 @@ npm run lint / cargo clippy / etc. If anything fails, fix it. Re-run until clean. Include evidence in your report. -**Check your own changes with `jj diff` (or `git diff`).** This shows what YOU changed in the current session. If you edited a file and then grep the file to check whether a change was applied, you'll see your own edit and may falsely conclude it was "already there." Always check the VCS diff to know what you actually changed vs what was already there. +**Check your own changes with `jj diff` (or `git diff`).** This shows what YOU changed in the current session. When using git, check the VCS diff to know what you actually changed vs what was already there. When using jj, edits are automatically tracked, so the current change will show your edits. compare against a previous commit if uncertain. ### 5. Commit diff --git a/plugins/orual-plan-and-execute/agents/task-implementor.md b/plugins/orual-plan-and-execute/agents/task-implementor.md index e6038f8..6ca7ed7 100644 --- a/plugins/orual-plan-and-execute/agents/task-implementor.md +++ b/plugins/orual-plan-and-execute/agents/task-implementor.md @@ -57,7 +57,7 @@ npm run lint / cargo clippy / etc. If anything fails, fix it. Re-run until clean. Include evidence in your report. -**Check your own changes with `jj diff` (or `git diff`).** This shows what YOU changed in the current session. If you edited a file and then grep the file to check whether a change was applied, you'll see your own edit and may falsely conclude it was "already there." Always check the VCS diff to know what you actually changed vs what was already there. +**Check your own changes with `jj diff` (or `git diff`).** This shows what YOU changed in the current session. When using git, check the VCS diff to know what you actually changed vs what was already there. When using jj, edits are automatically tracked, so the current change will show your edits. compare against a previous commit if uncertain. ### 5. Commit -- knotmirror 0.0.1