OpenParable
Skip to content
← Back to skills

Qv Dev Diary

Productivity
qv-dev-diary

Qv Dev Diary is an Agent Skill for productivity published in the tetherto/qvac repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Read, 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.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/tetherto/qvac/blob/HEAD/.cursor/skills/qv-dev-diary/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/qv-dev-diary, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Dev Diary

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 .cursor/skills/_lib/developer-workflow/diary-cli.mjs --status

Read today's diary:

node .cursor/skills/_lib/developer-workflow/diary-cli.mjs --read

Read a specific date:

node .cursor/skills/_lib/developer-workflow/diary-cli.mjs --read YYYY-MM-DD

Print the diary file path:

node .cursor/skills/_lib/developer-workflow/diary-cli.mjs --path YYYY-MM-DD

Append an entry:

node .cursor/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:

  1. Get the path with --path.
  2. Read the file with ReadFile.
  3. Edit only the requested entry.
  4. Preserve the existing markdown structure.

Do not put diary contents in repo files. Do not commit diary files.