Guide users through TCR (Test && Commit || Revert), TCRDD, and git-gamble workflows. ALWAYS trigger when a user mentions TCR, TCRDD, "test commit revert", "git gamble", or "git-gamble". Trigger when a user wants to combine TDD with automatic commits/reverts, enforce baby steps via a commit-or-revert loop, or asks…
PRD-driven delivery loop with a token-lean audit trail (requests → decisions → specs → tasks → commits). All docs/ log access goes through ./scripts/owl. Use for any feature, bug fix, or change in a repo using ATHENA docs/.
Ingests open retro issues, investigates via scramstorm, dispatches scram team to address changes, bumps version, comments on issues, commits and pushes.
A software-development workflow that turns a written request into a specification, an execution plan, code changes, tests, and commits. A specification describes what should be built; a plan describes how.
Drive a task queue (loop-tasks.md) to completion in ANY repo. Detect the repo's own rules, then for each task plan -> /review-plan -> implement -> verify -> /review -> fix all findings -> /battle-test -> commit -> push -> client doc -> mark done. Each task runs in its OWN subagent (context isolation, token-cheap); the…
Lightweight pre-commit workflow that splits atomic candidates, validates an index-only snapshot, runs direct checks, and performs a targeted review before creating a safe, approved commit.
Weekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware: breaks down per-person contributions with praise and growth areas.
Guide commit collaboration under team git commit conventions. Use when the user asks to prepare a commit, split changes into focused commits, generate a compliant commit message, decide AI-NONE vs AI-USE, or amend the latest local commit safely.
Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive…
Run the full pre-PR review per AGENTS.md §7 — gates, tagged diff walk, pessimistic meta-check, acceptance-criteria mapping, commit hygiene, rebase status, PR-description draft. Use when the human says "ship it", "ready to PR", "open the PR", "pre-PR check", or invokes /pre-pr.
Commit changes across the LiteStack meta-repo and its submodules. Use when the user asks to commit or push from the LiteStack root. It commits inside each changed submodule first, then records the updated submodule pointers in the meta-repo, and pushes according to the operating mode (template vs derived).
Reimplement a messy git branch with clean, narrative-quality commit history suitable for code review. Use when a branch has WIP commits, debug commits, or trial-and-error history that needs to be transformed into a reviewable story before creating a PR.
A repository setup skill that adds a reusable structure for working with coding agents, including instructions, skills, hooks, shared session state, and code checks.
Review pending git changes and create senior-quality commits. Groups unrelated changes into separate logical commits, writes Conventional Commits messages that explain the why, and executes them — all on a tight token budget. Use when the user says "commit", "commit my changes", "commit like a pro", "ship this", or…
Create standardized, semantic git commits using the Conventional Commits specification. Analyze the actual diff to determine appropriate type, scope, and message.
A read-only tool that examines changes in a Git worktree, the folder containing a repository and its current edits, then drafts a commit message and a pull request (PR) title and description. If there are no current edits, it uses recent commits instead.
Generates conventional Git commit messages from staged or unstaged code changes. Use when the user asks to commit, write a commit message, stage changes, or says things like "commit this", "what should my commit say", or "generate a commit message".
★not rated 2 2mo agoA56 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: