karajan-code 4.41.0 → 4.43.0

package/templates/roles/coder.md

@@ -119,13 +119,13 @@ When modifying an existing project:
 - NEVER overwrite existing files entirely. Always make targeted, minimal edits.
 - When adding new code to an existing file, insert only the new lines at the correct location.
 - After each edit, verify with `git diff` that ONLY the intended lines changed.
-- If unintended changes are detected, revert immediately with `git checkout -- <file>`.
+- If unintended changes are detected, undo ONLY those hunks with a targeted edit. Never revert the whole file: it may hold edits that are not yours.
 - Pay special attention to CSS, HTML, and config files where full rewrites destroy prior work.
 
 ## Code Quality Rules
 
 - Follow SOLID principles. Write small, focused functions (< 30 lines).
-- Make atomic commits: 1 logical change = 1 commit. Keep PRs small and reviewable.
+- One logical change per task; keep it small and reviewable. NEVER run git commit or git push: the pipeline commits once the review approves.
 - Security: use httpOnly cookies for auth tokens, validate all input, parameterize queries, never expose secrets.
 - No console.log in production code -- use a structured logger. No 'any' types -- use JSDoc annotations.
 

package/templates/roles/refactorer.md

@@ -22,7 +22,7 @@ You are the **Refactorer** in a multi-role AI pipeline. Your job is to improve c
 
 - NEVER overwrite existing files entirely. Always make targeted, minimal edits.
 - After each edit, verify with `git diff` that ONLY the intended lines changed.
-- If unintended changes are detected, revert immediately with `git checkout -- <file>`.
+- If unintended changes are detected, undo ONLY those hunks with a targeted edit. Never revert the whole file: it may hold edits that are not yours.
 
 ## Output format
 

package/templates/skills/kj-code.md

@@ -40,7 +40,7 @@ After writing code, verify ALL of these before reporting done:
 
 - NEVER overwrite existing files entirely — make targeted edits
 - After each edit, verify with `git diff` that ONLY intended lines changed
-- If unintended changes detected, revert immediately with `git checkout -- <file>`
+- If unintended changes are detected, undo ONLY those hunks with a targeted edit. Never revert the whole file: it may hold edits you did not make, and an agent never discards changes that are not its own
 
 ## Completeness check
 

package/templates/skills/kj-review.md

@@ -8,7 +8,7 @@ Review the changes in the current branch: $ARGUMENTS
 
 ## Steps
 
-1. Run `git diff main...HEAD` (or appropriate base branch) to see all changes
+1. See ALL the work: `git diff --cached` (staged), `git diff` (unstaged) and `git diff main...HEAD` (or the appropriate base branch) for what is already committed
 2. Review each changed file against the priorities below
 3. Report findings clearly
 

package/templates/skills/kj-sonar.md

@@ -13,14 +13,15 @@ $ARGUMENTS
    ```bash
    npx @sonar/scan -Dsonar.host.url=http://localhost:9000 -Dsonar.projectKey=<project-key>
    ```
-3. Check quality gate status:
+3. Check quality gate status (the token comes from `KJ_SONAR_TOKEN`, set by `kj init`; a token authenticates as `token:` with an empty password):
    ```bash
-   curl -s -u admin:admin "http://localhost:9000/api/qualitygates/project_status?projectKey=<project-key>"
+   curl -s -u "$KJ_SONAR_TOKEN:" "http://localhost:9000/api/qualitygates/project_status?projectKey=<project-key>"
    ```
 4. List issues:
    ```bash
-   curl -s -u admin:admin "http://localhost:9000/api/issues/search?projectKeys=<project-key>&statuses=OPEN&ps=50"
+   curl -s -u "$KJ_SONAR_TOKEN:" "http://localhost:9000/api/issues/search?projectKeys=<project-key>&statuses=OPEN&ps=50"
    ```
+   Never authenticate with the default `admin` account: if the server still accepts its default password, tell the user to change it.
 
 ## If SonarQube is not available