myxelium/Toju
1
0
Fork 0
Code Issues 16 Pull Requests Actions Packages Projects 2 Releases 39 Wiki Activity

chore: cheap named-bug path and prefer lint:fix

Browse Source 
Wire fix-bug prompts to a single Obsidian note plus default scope, and require npm run lint:fix instead of hand-fixing auto-fixable lint/format.

Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
myxelium
2026-07-22 21:49:06 +02:00
co-authored by Cursor
parent cfe10907be
commit 34c32ba64a
6 changed files with 56 additions and 73 deletions
Download Patch File Download Diff File Expand all files Collapse all files
AGENTS.md
+8 -3
View File
@@ -11,6 +11,10 @@ Agents **cannot** open a new Cursor chat. To reset context:
**At session start:** if `agents-docs/HANDOFF.md` has `Status: active`, read it first and continue Next steps. Do not redo Completed work.
## Named Obsidian bugs
When the user says `fix bug "…"`, follow `agents-docs/BUG_TRACKER.md` § Named fix: open **that one** vault note under `Log/Bugs/`, use it as acceptance criteria, fix in default scope, then set `status: Resolved`. Do not scan the whole bug inbox.
## Default work scope (token fence)
Unless the user **explicitly** expands scope, stay inside:
@@ -76,8 +80,9 @@ Skip full red-green for docs/copy/agent text, formatting, trivial wiring already
### Lint / type correctness (scoped)
1. Targeted Vitest under `toju-app/` (and colocated Electron specs only if you changed those files).
2. `npm run lint` — fix errors; do not paste entire lint logs into the chat.
3. `npm run build` when client types/templates could break; `npm run build:electron` only if you changed Electron sources.
2. Auto-fix style first: `npm run lint:fix` from repo root (`format` + `sort:props` + `eslint . --fix`). Do **not** hand-edit formatting/import-sort/eslint-fixable issues — re-run `lint:fix`. Then confirm clean with `npm run lint` only if you need a no-write check; prefer trusting `lint:fix` exit 0.
3. Do not paste entire lint logs into the chat — fix via `lint:fix` / minimal code changes for non-auto issues.
4. `npm run build` when client types/templates could break; `npm run build:electron` only if you changed Electron sources.
Do **not** run `cd server && npm run build` or `npm run test:e2e` unless scope expanded or the bug is proven there.
@@ -91,7 +96,7 @@ IPC/preload/WS contract changes → `agents-docs/features/<slug>.md` when that c
- [ ] Asked behavior proven (not only unit tests green)
- [ ] Stayed in scope (`toju-app` + targeted `electron` + CI) unless user expanded it
- [ ] Appropriate targeted tests for logic changes
- [ ] Lint/build only for touched packages
- [ ] Lint via `npm run lint:fix` (not hand-fixed style); build only touched packages
- [ ] Docs only if contracts changed
- [ ] Lesson + index entry if corrected this session
- [ ] If the thread is long and work remains: write `HANDOFF.md` and ask user for a new chat