blitztext-app-linux/AGENTS.md
google-labs-jules[bot] 9a00d480a2 Add Jules agent prompt and journal files and AGENTS.md rules
Co-authored-by: mARTin-B78 <91568406+mARTin-B78@users.noreply.github.com>
2026-06-08 19:25:38 +00:00

49 lines
1.8 KiB
Markdown

# Jules Agents
## Shared rules (every agent obeys these)
**Environment / verify** — mirror CI (`.github/workflows/ci.yml`):
```bash
sudo apt-get update && sudo apt-get install -y \
python3-gi gir1.2-gtk-3.0 gir1.2-appindicator3-0.1 \
libgirepository1.0-dev libcairo2-dev python3-dev
cd linux
pip install -r requirements.txt && pip install pytest ruff PyGObject
python -m py_compile blitztext/*.py # syntax gate
PYTHONPATH=. pytest tests # test gate
ruff check blitztext tests # quality gate
```
**Scope discipline**
- **One concern, one small PR.** No drive-by refactors (the repo's CONTRIBUTING
says so explicitly).
- **If there's no clear, high-confidence win this run, STOP — don't open a PR.**
- Check existing open PRs/branches first; never duplicate another agent's work.
- Never touch `requirements.txt`, `pyrightconfig.json`, or CI without it being
the explicit point of the task (Keeper/Polish own those).
- Never commit secrets, real audio, transcripts, or private endpoint URLs (the
CI secret scan will fail you anyway).
- Bump `linux/blitztext/__init__.py` + add a `CHANGELOG.md` entry for any
user-visible change. SemVer: fix → patch, feature → minor.
**Journal** — read `.jules/<name>.md` first; append only *critical, codebase-
specific* learnings (a real gotcha, a rejected change + why), never routine logs.
Format:
```markdown
## YYYY-MM-DD — [Title]
**Learning:** …
**Action:**
```
**PR format**
```markdown
Title: "<emoji> <Name>: <one-line change>"
Body:
💡 What — the change
🎯 Why — the problem it solves
⚠️ Risk — blast radius + how mitigated
🔬 Verified — exact commands run (py_compile / pytest / ruff / build-deb)
📎 Scope — files touched; confirm no unrelated changes
```