Compare commits
4 Commits
1bf47c4527
...
8948858c86
| Author | SHA1 | Date | |
|---|---|---|---|
|
8948858c86
|
|||
|
3e89662e72
|
|||
|
9674771c35
|
|||
|
fc185e1121
|
+114
-7
@@ -1,7 +1,114 @@
|
|||||||
# AI sessions and project overviews
|
# id: gi-patterns-54143085ec229f3cf907a5aa2a8fcade
|
||||||
.remember
|
# Created by https://www.toptal.com/developers/gitignore/api/linux
|
||||||
.gemini*
|
# Edit at https://www.toptal.com/developers/gitignore?templates=linux
|
||||||
.claude*
|
|
||||||
CLAUDE.md
|
### Linux ###
|
||||||
GEMINI.md
|
*~
|
||||||
AGENTS.md
|
|
||||||
|
# temporary files which can be created if a process still has a handle open of a deleted file
|
||||||
|
.fuse_hidden*
|
||||||
|
|
||||||
|
# KDE directory preferences
|
||||||
|
.directory
|
||||||
|
|
||||||
|
# Linux trash folder which might appear on any partition or disk
|
||||||
|
.Trash-*
|
||||||
|
|
||||||
|
# .nfs files are created when an open file is removed but is still being accessed
|
||||||
|
.nfs*
|
||||||
|
|
||||||
|
# End of https://www.toptal.com/developers/gitignore/api/linux
|
||||||
|
|
||||||
|
# id: gitig-boilerplate-92f3a89d2c63f6a381be8bebd1862de5
|
||||||
|
# ╭──────────────────────────────────────────────────────────╮
|
||||||
|
# │ GitIgnore Boilerplate Template │
|
||||||
|
# ╰──────────────────────────────────────────────────────────╯
|
||||||
|
#
|
||||||
|
# ──────────────────── OS-Generated Files ────────────────────
|
||||||
|
# automatic backup files created by some editors (e.g., Vim, Emacs)
|
||||||
|
*~
|
||||||
|
|
||||||
|
# temporary files created if a process still has a handle to a deleted file
|
||||||
|
.fuse_hidden*
|
||||||
|
|
||||||
|
# KDE directory preferences
|
||||||
|
.directory
|
||||||
|
|
||||||
|
# MacOS junk
|
||||||
|
.DS_Store
|
||||||
|
Thumbs.db
|
||||||
|
|
||||||
|
# Linux trash folder which might appear on any partition or disk
|
||||||
|
.Trash-*
|
||||||
|
|
||||||
|
# files created when an open file is removed but is still being accessed
|
||||||
|
.nfs*
|
||||||
|
|
||||||
|
# ─────────────────── Debug/Temporary/Testing ────────────────
|
||||||
|
# Matches OLD / .OLD
|
||||||
|
[Oo][Ll][Dd]/
|
||||||
|
.[Oo][Ll][Dd]/
|
||||||
|
|
||||||
|
# Matches DISABLE / .DISABLE
|
||||||
|
[Dd][Ii][Ss][Aa][Bb][Ll][Ee]/
|
||||||
|
.[Dd][Ii][Ss][Aa][Bb][Ll][Ee]/
|
||||||
|
|
||||||
|
# Matches DISABLED / .DISABLED
|
||||||
|
[Dd][Ii][Ss][Aa][Bb][Ll][Ee][Dd]/
|
||||||
|
.[Dd][Ii][Ss][Aa][Bb][Ll][Ee][Dd]/
|
||||||
|
|
||||||
|
# Matches DEBUG / .DEBUG
|
||||||
|
[Dd][Ee][Bb][Uu][Gg]/
|
||||||
|
.[Dd][Ee][Bb][Uu][Gg]/
|
||||||
|
|
||||||
|
# Matches TMP / .TMP
|
||||||
|
[Tt][Mm][Pp]/
|
||||||
|
.[Tt][Mm][Pp]/
|
||||||
|
|
||||||
|
# Matches TEMP / .TEMP
|
||||||
|
[Tt][Ee][Mm][Pp]/
|
||||||
|
.[Tt][Ee][Mm][Pp]/
|
||||||
|
|
||||||
|
# Matches TEMPORARY / .TEMPORARY
|
||||||
|
[Tt][Ee][Mm][Pp][Oo][Rr][Aa][Rr][Yy]/
|
||||||
|
.[Tt][Ee][Mm][Pp][Oo][Rr][Aa][Rr][Yy]/
|
||||||
|
|
||||||
|
# Matches TESTING / .TESTING
|
||||||
|
[Tt][Ee][Ss][Tt][Ii][Nn][Gg]/
|
||||||
|
.[Tt][Ee][Ss][Tt][Ii][Nn][Gg]/
|
||||||
|
|
||||||
|
# ─────────────────── AI Sessions and Rules ──────────────────
|
||||||
|
# Matches CLAUDE.md, .claud*, etc.
|
||||||
|
[Cc][Ll][Aa][Uu][Dd][Ee].[Mm][Dd]
|
||||||
|
.[Cc][Ll][Aa][Uu][Dd]*
|
||||||
|
|
||||||
|
# Matches GEMINI.md, .gemin*, etc.
|
||||||
|
[Gg][Ee][Mm][Ii][Nn][Ii].[Mm][Dd]
|
||||||
|
.[Gg][Ee][Mm][Ii][Nn]*
|
||||||
|
|
||||||
|
# Matches ANTIGRAVITY.md, .antigrav*, etc.
|
||||||
|
[Aa][nN][Tt][Ii][Gg][Rr][Aa][Vv][Ii][Tt][Yy].[Mm][Dd]
|
||||||
|
.[Aa][Nn][Tt][Ii][Gg][Rr][Aa][Vv]*
|
||||||
|
|
||||||
|
# Matches AGENTS.md, .remember, etc.
|
||||||
|
[Aa][Gg][Ee][Nn][Tt][Ss].[Mm][Dd]
|
||||||
|
.[Rr][Ee][Mm][Ee][Mm][Bb][Ee][Rr]
|
||||||
|
|
||||||
|
# ──────────────────── Planning Artifacts ───────────────────
|
||||||
|
# Catalog files generated by pre-implementation analysis passes
|
||||||
|
.superpowers
|
||||||
|
docs/superpowers
|
||||||
|
docs/specs
|
||||||
|
|
||||||
|
# ──────────────────────────────────────────────────────────────
|
||||||
|
|
||||||
|
# ──────────────── Added by agents-init ──────────────────
|
||||||
|
# agents-init --agents
|
||||||
|
AGENTS/
|
||||||
|
# ────────────────────────────────────────────────────────
|
||||||
|
|
||||||
|
# ──────────────── Added by agents-init ──────────────────
|
||||||
|
# agents-init --plugins
|
||||||
|
docs/plans
|
||||||
|
docs/devlogs
|
||||||
|
# ────────────────────────────────────────────────────────
|
||||||
|
|||||||
@@ -12,6 +12,9 @@ Skills are plain Markdown files. The included `install.sh` script handles discov
|
|||||||
- [systematic-enumeration](#systematic-enumeration)
|
- [systematic-enumeration](#systematic-enumeration)
|
||||||
- [git-publish-workflow](#git-publish-workflow)
|
- [git-publish-workflow](#git-publish-workflow)
|
||||||
- [readme-sync-audit](#readme-sync-audit)
|
- [readme-sync-audit](#readme-sync-audit)
|
||||||
|
- [docs-sync-audit](#docs-sync-audit)
|
||||||
|
- [date-time](#date-time)
|
||||||
|
- [technical-devlog-scribe](#technical-devlog-scribe)
|
||||||
- [ship-it](#ship-it)
|
- [ship-it](#ship-it)
|
||||||
- [Installation](#installation)
|
- [Installation](#installation)
|
||||||
- [Quick Install (curl)](#quick-install-curl)
|
- [Quick Install (curl)](#quick-install-curl)
|
||||||
@@ -67,13 +70,49 @@ Three-phase execution:
|
|||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
|
### `docs-sync-audit`
|
||||||
|
|
||||||
|
**Purpose:** Keep documentation accurate by aligning the project's Single Source of Truth (SSoT) with the current state of the codebase.
|
||||||
|
|
||||||
|
Unlike `readme-sync-audit`, this skill first discovers the documentation root. If a dedicated `docs/`, `wiki/`, or site config (e.g. `mkdocs.yml`) exists, it is treated as the SSoT and receives the detailed updates; the `README.md` is then kept as a high-level landing page that links into it. If no docs directory exists, it falls back to `README.md` as the SSoT.
|
||||||
|
|
||||||
|
Three-phase execution:
|
||||||
|
|
||||||
|
1. **Delta Analysis** — locate the last commit that touched the SSoT, diff all code changes to `HEAD`, and extract undocumented environment variables, CLI flags, or API changes.
|
||||||
|
2. **Pruning & Update Audit** — route detailed changes to the correct files, remove stale steps, correct versions and paths, and synthesize docs for new features.
|
||||||
|
3. **Structural Integrity Check** — verify Quick Start commands, configuration keys, and usage examples still match the implementation.
|
||||||
|
|
||||||
|
**Use when:** you say "Update the docs," "Sync the wiki," or invoke `/docs-sync-audit`.
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
### `date-time`
|
||||||
|
|
||||||
|
**Purpose:** Retrieve the exact, real-time current date and time when a task depends on the present moment.
|
||||||
|
|
||||||
|
The skill runs the system `date` command rather than guessing, then uses the result for time-sensitive reasoning.
|
||||||
|
|
||||||
|
**Use when:** the request asks for the current date/time, uses relative expressions ("today", "next week", "recently"), or needs an age, duration, countdown, or check of whether an event has already occurred.
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
### `technical-devlog-scribe`
|
||||||
|
|
||||||
|
**Purpose:** Produce a dense, objective technical summary of a development session as a durable historical record optimized for future context loading.
|
||||||
|
|
||||||
|
The skill writes a structured Markdown file to `AGENTS/devlogs/<kebab-case-short-description>.md`, with YAML frontmatter (date, title, tags, status) followed by the session summary. It relies strictly on what happened in the session — no hallucinated external constraints — and avoids conversational filler.
|
||||||
|
|
||||||
|
**Use when:** you say "session wrap-up," "write a devlog," "done for the day," or want an auditable record of what changed and why.
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
### `ship-it`
|
### `ship-it`
|
||||||
|
|
||||||
**Purpose:** Run a comprehensive pre-flight audit and publish changes to a new PR in a single command.
|
**Purpose:** Run a comprehensive pre-flight audit and publish changes to a new PR in a single command.
|
||||||
|
|
||||||
Two sequential phases — Phase 2 is blocked until Phase 1 succeeds:
|
Two sequential phases — Phase 2 is blocked until Phase 1 succeeds:
|
||||||
|
|
||||||
1. **Documentation Sync & Code Audit** — acts as `/readme-sync-audit`: scans all file changes since the last README edit, updates the README to match the current codebase, and audits code files for syntax errors or regressions. **Halts the entire workflow** if any breaking issue is found.
|
1. **Documentation Sync & Code Audit** — acts as `/docs-sync-audit`: scans all file changes since the last documentation edit, updates the docs/README to match the current codebase, and audits code files for syntax errors or regressions. **Halts the entire workflow** if any breaking issue is found.
|
||||||
2. **Git Publish Workflow** — acts as `/git-publish-workflow`: creates a descriptively named branch, commits all pending changes (including the README updates from Phase 1), pushes to the remote, and opens a Pull Request against `main`.
|
2. **Git Publish Workflow** — acts as `/git-publish-workflow`: creates a descriptively named branch, commits all pending changes (including the README updates from Phase 1), pushes to the remote, and opens a Pull Request against `main`.
|
||||||
|
|
||||||
**Use when:** you say "Ship this," "Publish my changes," or invoke `/ship-it`.
|
**Use when:** you say "Ship this," "Publish my changes," or invoke `/ship-it`.
|
||||||
|
|||||||
+2
-1
@@ -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.",
|
"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.",
|
"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.",
|
"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."
|
||||||
}
|
}
|
||||||
|
|||||||
@@ -1,4 +1,11 @@
|
|||||||
# Skill Name: Current Date and Time Retrieval
|
---
|
||||||
|
name: date-time
|
||||||
|
description: Retrieves the exact current date and time for time-sensitive queries, scheduling, duration calculations, and validating chronological context.
|
||||||
|
version: 1.0.0
|
||||||
|
user-invocable: true
|
||||||
|
---
|
||||||
|
|
||||||
|
# Current Date and Time Retrieval
|
||||||
|
|
||||||
## Purpose
|
## Purpose
|
||||||
Enables the assistant to retrieve the exact, real-time current date and time when addressing time-sensitive queries, scheduling tasks, calculating durations, or validating chronological context.
|
Enables the assistant to retrieve the exact, real-time current date and time when addressing time-sensitive queries, scheduling tasks, calculating durations, or validating chronological context.
|
||||||
|
|||||||
@@ -1,5 +1,11 @@
|
|||||||
Name: /ship-it
|
---
|
||||||
Description: Run a comprehensive pre-flight audit, sync the README, and publish the changes to a new PR.
|
name: ship-it
|
||||||
|
description: Runs a comprehensive pre-flight audit, syncs the README, and publishes the changes to a new PR.
|
||||||
|
version: 1.0.0
|
||||||
|
user-invocable: true
|
||||||
|
---
|
||||||
|
|
||||||
|
# /ship-it
|
||||||
|
|
||||||
Instructions:
|
Instructions:
|
||||||
Execute the following two phases sequentially. Do not proceed to Phase 2 unless Phase 1 completes successfully.
|
Execute the following two phases sequentially. Do not proceed to Phase 2 unless Phase 1 completes successfully.
|
||||||
|
|||||||
@@ -1,9 +1,8 @@
|
|||||||
---
|
---
|
||||||
name: Systematic Enumeration
|
name: systematic-enumeration
|
||||||
description: Forces element-by-element verification for finite sets to prevent counting errors.
|
description: Forces element-by-element verification for finite sets to prevent counting errors.
|
||||||
version: 1.0
|
version: 1.0.0
|
||||||
user-invocable: true
|
user-invocable: true
|
||||||
disable-model-invocation: false
|
|
||||||
---
|
---
|
||||||
|
|
||||||
# Systematic Enumeration & Verification Skill
|
# Systematic Enumeration & Verification Skill
|
||||||
|
|||||||
@@ -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>
|
||||||
|
---
|
||||||
Reference in New Issue
Block a user