rootiest/ai-skills
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: add technical-devlog-scribe skill

Browse Source 
Generates a structured, objective technical summary of a development session, saved to AGENTS/devlogs/. Registers it in descriptions.json.
This commit is contained in:
Rootiest
2026-06-17 22:19:12 -04:00
parent 1bf47c4527
commit fc185e1121
2 changed files with 33 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
descriptions.json
+2 -1
View File
@@ -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."
}
skills/technical-devlog-scribe/SKILL.md
+31
View File
@@ -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/<kebab-case-short-description>.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: <Clear, concise title>
tags: [<relevant>, <tech>, <stack>, <tags>]
status: <Complete | In-Progress | Blocked>
---