agentleFS
Sign inStart free
tethertotetherto/qvac/.agents/skills/qv-dev-diary/SKILL.md

qv-dev-diary

Skill697 starsChanged 18 days agoApache-2.0View on GitHub

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.

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read today's diary:

    line 21
  2. Distinctive:

    Read a specific date:

    line 27
  3. Very specific:

    Read the file with ReadFile.

    line 50
  4. Distinctive:

    Do not put diary contents in repo files.

    line 54

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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 .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:

  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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free