Skill UI

This skill analyzes the comprehensive commit history between two branches to generate a concise, objective, and highly structured Pull Request (PR) description. It automatically groups changes by domain, summarizing the purpose, technical notes, and user impact, ensuring consistency and minimizing manual documentation effort.

This skill analyzes raw git diffs or change descriptions to generate clear, story-driven commit messages. It strictly adheres to the Conventional Commits specification, ensuring that messages thoroughly explain *why* a change was made, not just *what* changed. It is ideal for writing meaningful commit history, preparing pull requests, or summarizing complex code changes for team collaboration.

This skill generates structured and standardized Git commit messages following the Conventional Commits specification. By analyzing code changes (via diff or status), it helps developers automatically create clear, actionable, and searchable commit history messages, ensuring consistency across the project.

This meta-skill is designed to automate the diagnosis of complex programming errors. When presented with a stack trace, traceback, or failing log, it orchestrates a multi-step investigation. It parses the trace, searches the repository history, checks relevant issues, and analyzes code diffs to provide a comprehensive brief for root cause analysis and debugging.

This skill allows users to mine their extensive coding history across various AI agents (Claude, Codex, Gemini, etc.) into a persistent, structured corpus. It surfaces reproducible workflows as evidence and interactively helps the user forge these past practices into reusable, installed skills across their agent ecosystem. It is designed to synthesize judgment from raw transcripts into actionable, portable skills.

This skill provides a deterministic, git-only method to verify claims made by AI agents (e.g., 'done', 'shipped', 'fixed'). Instead of trusting the agent's self-report, it audits the commit's diff and git history using the DOS kernel (`dos verify`, `dos commit-audit`) to confirm if the claimed change genuinely occurred and is backed by non-forgeable evidence. It acts as a critical quality gate.

This skill reconstructs the detailed workflow behind a specific coding artifact (like a feature or PR). By analyzing local `ax` agent traces, it connects commits, sessions, skills, and tool calls into a concise, evidence-grounded narrative. It is used when needing to understand the step-by-step process and key decisions that led to a result.

Plaso (log2timeline) is an open-source engine used to generate forensic super-timelines. This skill guides the process of normalizing hundreds of diverse artifact types—including MACB times, registry keys, EVTX logs, and browser history—into a single, cohesive chronological view. The workflow covers extraction, filtering, and importing the timeline into Timesketch for collaborative analysis, which is crucial for incident response, correlating complex activity chains, and detecting anti-forensic techniques like timestomping.

A comprehensive tool for exploring Go/Golang packages and modules using the pkg.go.dev API via the `godig` client. It provides read-only access to essential information, including detailed API signatures, comprehensive documentation, version history, dependency graphs, known vulnerabilities (CVEs), and import usage. Ideal for researching external Go libraries, verifying API usage, or understanding module structure.

Workthreads analyzes a team's coding history across multiple repositories to generate a structured weekly status report. It clusters raw logs into 'work threads' and automatically tags their lifecycle status (new, open loops, closed, reverted). This is essential for leads needing a high-level, actionable summary of project progress, outstanding tasks, and completed features without reading thousands of lines of raw activity.

This skill automatically rewrites raw commit messages to adhere to professional engineering standards. It strips out common 'AI/marketing slop' phrases (like 'robust implementation' or 'leverage') while strictly maintaining the Conventional Commits format. It ensures subjects are concise, bodies provide necessary context (why, breaking changes), and the tone is direct and actionable, making your project history clean and readable.