Use at a specflo project's execute phase, when turning a validated plan.md into committed, verified code one task at a time. Triggers include "execute the plan", "start building", "work the next task", or specflo status showing the execute phase. Do NOT use before a plan has been validated, or for trivial fixes…
Use 901 to run one feature end-to-end through SpecFlow's full pipeline as a single git-tracked run: high-level design, happy-path specs, scenario-by-scenario test-driven build-out validated and committed per module, cleanup, an optional expanded-coverage round, and a merge back to the base branch. Every design/spec…
Capture the intent behind staged changes as a provenance doc in docs/intents/, extracted from the Claude Code and Cursor chats that produced the code. Use when the user asks to generate or preview an intent doc, capture commit intent, check why the pre-commit intent hook skipped or failed, or run its self-test.
Full implementation mode - end-to-end feature implementation with phased execution, parallel work streams, verification gates, and atomic commits per phase.
Run the project's validation (/check), and on green stage + commit your changes using the project's /commit conventions; on red, report a blocker and note the Queen without committing. Use when the user asks to checkpoint, save progress, or commit safely mid-task.
One tick of the GitHub maintenance loop for the repository named in .loop/config.json: send what the maintainer already approved, triage the issues created in the configured window, fix what is worth fixing test-first, follow the owner's own pull requests through CI, review and merge, and draft every outbound action…
Use this skill for ANY git operation — commits, pushes, PRs, releases, or version tagging. Triggers on: "commit", "push", "save my changes", "create a PR", "open a pull request", "ship this", "make a release", "tag this version", "checkpoint my work", or any request to record or publish code changes. Produces…
Writes git commit messages in a pure human-authored voice and strips AI attribution, tool watermarks, model names, co-author footers, and AI self-references. Use whenever creating, amending, rewriting, or reviewing a git commit message, including when running git commit, writing PR titles, or drafting commit bodies.
Write git commit messages that follow the Conventional Commits standard. Use when the user asks for a commit message, or gives a change summary or diff and wants it written up for git.
Rédige un message de commit Git pour un projet PHP/Symfony, en suivant la convention Emoji-Log. À utiliser dès que l'utilisateur demande un commit ou un message de commit.
Close a session cleanly — write this project's handoff (/.claude/handoffs/ .md), report git state and running work, triage the inbox, propose user-wide conventions, file global knowledge, push the vault. Add "and ship" to also commit and push the project repo.
Publish task-scoped changes to GitHub through a branch/commit/push/PR flow, including fork-based external contributions. Use when the user wants changes pushed or a PR opened; draft PR is the default.
A project-history documentation generator that examines Git commits, project documents, and source code to explain how a codebase changed over time.
★not rated 5 7mo agoA126 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: