Add TokenJuice output compaction guidance - #2
Conversation
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (22)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Two pieces previously living only in the production workspace: skills/note/SKILL.md Obsidian-formatted note creation skill. Two modes (verbatim fix, summarize/concept), YAML frontmatter requirement (3-5 tags + YYYY-MMM-DD created), full Obsidian callout vocabulary ([!bug], [!success], [!tip], [!warning], [!info], [!note], [!example], [!question]) with usage rules. Sync target is left configurable (rclone-to-gdrive, local vault, bisync timer). scripts/backup-restic.sh Twice-daily restic backup to two destinations: Google Drive via rclone and a local NAS mount. Encrypted, deduplicated, retention 7d/4w/3m. Conservative rclone throttling to survive Drive quota pressure. Skips NAS cleanly if not mounted. Sanitized paths and repo names. Plus two memory cards that explain when/why to use each: memory/cards/obsidian-notes.md Verbatim-vs-concept mode selection, callout vocabulary table, sync target shapes, when NOT to /note (durable agent knowledge belongs in cards, not the vault), relationship to the memory system. memory/cards/backup-restic.md Two-destination rationale (workstation-fail vs NAS-fail vs account-lock vs ransomware matrix), cadence (twice-daily 03/15), default paths and excludes, retention math, rclone throttle reasoning, NAS lockfile handling, recovery drill, monitoring hook, anti-patterns. Wired into the workspace profile manifest with the script marked executable. Tests cover both new files and the executable bit.
1 participant
Summary
Validation
.venv/bin/python -m pytest -q.venv/bin/solo-mise init --target /tmp/solo-mise-tokenjuice-smoke --profile workspace && test -f /tmp/solo-mise-tokenjuice-smoke/memory/cards/tokenjuice-output-compaction.md && .venv/bin/solo-mise doctor --target /tmp/solo-mise-tokenjuice-smokePYTHONPATH=$HOME/repos/content-guard/src python3 -m content_guard scan . --policy $HOME/repos/content-guard/policies/public-repo.jsongit push -u origin $(git branch --show-current)pre-push content-guard scan passed