Dev Diary
SkillDocs & knowledgeRead, inspect, and add local dev diary entries after diary setup. Use when the user asks to view today's diary, edit diary notes, add work to the diary, or check what has been logged.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Dev Diary skill
What this skill tells your AI
The instructions your AI receives, as published by tetherto/qvac in .agents/skills/qv-dev-diary/SKILL.md and read by ahel’s review.
Operate on the local diary after setup. This is not the setup skill; use qv-dev-diary-setup for initialization.
Diary files live under ~/.config/qvac-pr-skills/diary/ and are never committed.
Commands
Status:
node .agents/skills/_lib/developer-workflow/diary-cli.mjs --status
Read today's diary:
node .agents/skills/_lib/developer-workflow/diary-cli.mjs --read
Read a specific date:
node .agents/skills/_lib/developer-workflow/diary-cli.mjs --read YYYY-MM-DD
Print the diary file path:
node .agents/skills/_lib/developer-workflow/diary-cli.mjs --path YYYY-MM-DD
Append an entry:
node .agents/skills/_lib/developer-workflow/diary-cli.mjs --append '{"title":"Reviewed PR #123","summary":"Approved after checking tests.","type":"pr-review","pr":"123","ticket":"TICKET-123","status":"done"}'
Editing
To edit existing diary text:
- Get the path with
--path. - Read the file with
ReadFile. - Edit only the requested entry.
- Preserve the existing markdown structure.
Do not put diary contents in repo files. Do not commit diary files.
Signals
- GitHub stars
- 601
- Forks
- 111
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
qv-dev-diary- Source
- github.com/tetherto/qvac