From fc185e11215de98dd6007339cc7789eb403aa5b5 Mon Sep 17 00:00:00 2001 From: rootiest Date: Wed, 17 Jun 2026 22:19:12 -0400 Subject: [PATCH] feat: add technical-devlog-scribe skill Generates a structured, objective technical summary of a development session, saved to AGENTS/devlogs/. Registers it in descriptions.json. --- descriptions.json | 3 ++- skills/technical-devlog-scribe/SKILL.md | 31 +++++++++++++++++++++++++ 2 files changed, 33 insertions(+), 1 deletion(-) create mode 100644 skills/technical-devlog-scribe/SKILL.md diff --git a/descriptions.json b/descriptions.json index 8877ef4..c82ea15 100644 --- a/descriptions.json +++ b/descriptions.json @@ -4,5 +4,6 @@ "git-publish-workflow": "Automate the full lifecycle from uncommitted local work to an open Pull Request, with built-in quality gates.", "readme-sync-audit": "Keep README.md accurate by programmatically aligning it with the current state of the codebase.", "ship-it": "Run a comprehensive pre-flight audit and publish changes to a new PR in a single command.", - "systematic-enumeration": "Eliminate counting and membership errors via explicit set enumeration and atomic element testing." + "systematic-enumeration": "Eliminate counting and membership errors via explicit set enumeration and atomic element testing.", + "technical-devlog-scribe": "Generates a highly structured, objective technical summary of a development session." } diff --git a/skills/technical-devlog-scribe/SKILL.md b/skills/technical-devlog-scribe/SKILL.md new file mode 100644 index 0000000..1c1de46 --- /dev/null +++ b/skills/technical-devlog-scribe/SKILL.md @@ -0,0 +1,31 @@ +--- +name: technical-devlog-scribe +description: Generates a highly structured, objective technical summary of a development session. +version: 1.0.0 +user-invocable: true +--- + +# SKILL: Technical Devlog Scribe + +## Description +Generates a comprehensive, highly structured technical summary of a development session. This skill acts as an objective technical scribe, producing a reliable historical record optimized for future context loading and maintaining a single source of truth for project evolution. + +## System Directives +* **Tone & Style:** Maintain an objective, dense, and highly technical tone. Avoid conversational filler or fluff. +* **Accuracy:** Rely strictly on the actions, code snippets, and decisions discussed within the current session. Do not hallucinate external constraints. +* **File Routing:** The output must be saved directly to `AGENTS/devlogs/.md`. Ensure the filename is concise but descriptive (e.g., `AGENTS/devlogs/oauth2-token-refresh-fix.md`). + +## Required Output Structure + +The generated markdown file must adhere strictly to the following format: + +--- +**[START OF FILE FORMAT]** + +```yaml +--- +date: YYYY-MM-DD +title: +tags: [, , , ] +status: +---