A four-stage design-review command that reviews an architecture policy document, checks its consistency and impact, performs a security review, and applies the findings back to the document. It changes the design document, not the source-code implementation.
A coordinator for developing several GitHub Issues at the same time, from preparation and design through implementation, pull-request merging, user acceptance testing, and fixes. A worktree is a separate working folder for a Git branch, and UAT means checking that the finished change works for its users.
An automated workflow that takes a software issue from design review through a work plan and implementation. TDD, or test-driven development, means writing tests around the expected behavior as part of the development process.
An automated workflow that develops a GitHub issue from its requirements through tests, code changes, refactoring, documentation, user acceptance testing, and a progress report.
An automated project workflow that takes a GitHub issue through review, design, planning, and implementation. It uses TDD, or test-driven development, where tests guide the code changes.
A pull-request merge pipeline coordinates several completed feature branches, creates or reuses pull requests, waits for continuous-integration checks, merges them into develop in order, and runs an integration build. A pull request is a proposed code change for review; continuous integration automatically checks code changes.
A development progress report is a summary of an issue’s work, including test-driven development (TDD), testing, code cleanup, quality checks, and blockers. TDD means writing tests as part of guiding the implementation.
A code-refactoring command improves the structure and readability of existing code while keeping its behavior. Refactoring can include splitting large methods or classes, removing duplication, and improving names.
A command that repeats the fix-and-test process for issues that fail user acceptance testing, or UAT—the checks that confirm a feature works for its intended users.
User acceptance testing (UAT) is checking a change in a real device environment against the conditions written in an issue. This command plans, reviews, runs, and reports those checks.
An issue-based planning command that reads a GitHub Issue and turns it into a detailed implementation plan. It breaks the work into coding, testing, documentation, and dependency steps.
A cleanup command for removing the working environment linked to one or more GitHub Issues. It checks the issue numbers, stops issue-specific servers, and performs the documented worktree cleanup and synchronization steps.
A command that creates Git worktrees for one or more GitHub issues. A Git worktree is a separate working directory connected to the same Git repository, so work can happen in parallel.
A maintenance workflow for keeping slash-command catalog files aligned with the official command sources for each CLI, while recording what those sources contained.
A tested monitoring recipe for supervising parallel coding-agent workers, including state detection, intervention decisions, and completion checks. It includes Bash 3.2-compatible scripts and fixture-based tests, where fixtures are saved example outputs used to test the logic.
A server rebuild command stops a running server, builds the current or selected worktree, and starts the server again. A worktree is a separate working directory linked to a Git branch.
A release procedure for increasing a project’s version, merging changes from the develop branch into main, creating a tag and GitHub Release, and merging the result back. GitHub then publishes the package to npm automatically after the release.