Autonomous end-to-end pipeline. Runs /spec → /architect → /implement → /review → /wrapup like /proceed, but instead of pausing at each gate it routes the decision through the decision-maker agent, commits its work as it goes, and ends in a single final human review backed by a full audit log. Opt-in; conservative by…
Streamlined pipeline for bug fixes. Slimmer than /proceed — bug report → investigate → fix → verify → ship, with gates between each. Use for defects, not for new features. Larger or scope-creeping bugs should be re-framed as a REQ via /spec.
Command "healthcheck" from ulfaslak/memorable, covering documentation health check command, when to use this command, execution protocol, 1. architecture decisions verification and 2. api contracts verification.
When the user triggers this action, walk them through setting up Firecrawl for this project. Run each step automatically. Speak in plain, friendly language.
When the user triggers this command, walk them through setting up the Perplexity API for this project. Run each step automatically. Speak in plain, friendly language.
Cut a git-flow release from develop, infer the semver bump from commits since the last version tag, bump workspace versions, finish the release, push branches and tags, and publish a GitHub release. Use when shipping a new project release.
I've got an idea I want to talk through with you. I'd like you to help me turn it into a fully formed design and spec (and eventually an implementation plan) Check out the current state of the project in our working directory to understand where we're starting off, then ask me questions, one at a time, to help refine…
A command named create-pr for an Expo Updates Admin project. It includes guidance for creating a pull request, writing its summary, following the required steps, and using a pull-request template.
A command named newfeat for setting up a new feature. The description is partly in Chinese and does not provide enough detail about its exact behaviour.
★not rated 4 5mo agoA0 tokens
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: