mARTin-B78/tts-voice-creator-clone-and-design-2
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(qa): sonar-fixer reports and closes the GitHub issue

Browse Source 
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
mARTin-B78 2026-10-06 04:00:06 +02:00
parent b60586a559
commit 1963cdc0f4
1 changed files with 6 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
architecture/sonar-triage.md
View File

@ -53,4 +53,9 @@ npm run sonar:triage -- --apply --fix-small
Local fix commits: `git reset --hard <sha before>` / `git revert`. Issues: close the GitHub issue and the multica issue. Nothing is pushed by the script.
## sonar-fixer agent instructions
Fix only the given Sonar issue. Read CLAUDE.md and PROJECT_MAP.md first. Run `node scripts/check-frontend.mjs` and Python `unittest` with an isolated HOME; tests mock the API and import from tests/_guard.js. One local Conventional Commit `fix(sonar): ...`; never push; never touch secrets; if a design decision is needed, stop and comment.
Fix only the given Sonar issue. Read CLAUDE.md and PROJECT_MAP.md first. Run `node scripts/check-frontend.mjs` and Python `unittest` with an isolated HOME; tests mock the API and import from tests/_guard.js. Browser (Playwright) specs run against the live app and cannot see worktree edits: say which checks you did not run. One local Conventional Commit `fix(sonar): ...`; never push; never touch secrets; if a design decision is needed, stop and comment.
When done:
1. Comment on the multica issue: commit SHA, files changed, what you verified, checks NOT run, findings skipped as false positives (with reason).
2. Post the same report on the GitHub issue from `github_issue_url`: `gh issue comment <number> --body-file -` (paths and line numbers only, no code; say the commit is LOCAL and not pushed), add the label `fixed-local`, then close it: `gh issue close <number> --reason completed`. If you fixed only part of the findings, do NOT close it: list what is left in the comment.
3. If a design decision is needed or you could not fix it, comment on both issues and leave the GitHub issue open.