xonecas.io
64875
Mc

mini-coder / commit d8b4903

docs: point agents to known issues, improve audit skill

- AGENTS.md: add pointer to docs/KNOWN_ISSUES.md, move TODO.md
  guideline higher for visibility
- audit skill: require reading KNOWN_ISSUES.md in phase 1

xonecas2026-03-20 d8b490370d99971dc4b62530a027d71d1547fd4e parent 4887dc3

2 files changed

.agents/skills/audit/SKILL.md+1−1
@@ -10,7 +10,7 @@ Run a complete audit of the mini-coder implementation.
1010
1111 Audit the codebase against the project's core idea (the source of truth for design):
1212
13-1. Read the core idea section in AGENTS.md (or the system prompt context).
13+1. Read the core idea section in AGENTS.md (or the system prompt context). And the KNOWN_ISSUES.md files.
1414 2. Walk through each module and question design choices — stay compliant with the original idea.
1515 3. Employ KISS, DRY, and YAGNI — flag surprise additions or eager optimizations.
1616 4. Check `TODO.md` for known issues already tracked — don't duplicate them.
AGENTS.md+2−1
@@ -2,6 +2,8 @@
22
33 - App data folder is in `~/.config/mini-coder/`. It includes sqlite db file and logs.
44 - README.md is cosmetic for users, don't edit unless asked to.
5+- Known issues are in `docs` as well as the other man-like document about mini-coder.
6+- Create or reuse the `TODO.md` file to track your progress in long tasks. Remove completed items, keep it clean, concise, and up to date at all times. Track it in git.
57 - Write minimal tests, focused on our code's logic. Never test dependencies. Never use mocks or stubs.
68 - Keep the repo pristine: no failing tests, no lint, no build issues, no `ignore`-style comments. No failing hooks.
79 - Verify your changes, you can use the shell tool and `tmux` to test as needed.
@@ -13,7 +15,6 @@
1315 - Don't make random test files, if you need to test something, write a propper unit test.
1416 - If you make temp files, clean them up when you are done.
1517 - Use Conventional Commits formatting for commit messages. When you commit, include the whole diff unless told otherwise.
16-- Create or reuse the `TODO.md` file to track your progress in long tasks. Remove completed items, keep it clean and concise. Track it in git.
1718
1819 ## Core idea, treat this as the source of truth for the design/implementation.