An automated check that tests whether a feature meets the conditions written in a GitHub issue. It can run integration and end-to-end tests, which check how several parts work together and how the feature works from a user's point of view.
A command that records architecture-review findings in a project’s design document. It handles “Must Fix” and “Should Fix” items, but does not change source code.
A design-review command that examines a software design document or source folder for structure, performance, security, system fit, and technical risks.
An automated workflow for investigating, fixing, testing, and reporting software bugs. You provide a bug description and, optionally, logs, severity, or a related issue number.
A pull-request creation command that reads the current branch and linked GitHub Issue, checks the changes, and generates a pull request title and description. A pull request is a request to review and merge changes into a shared codebase.
A command for turning a bug description from a conversation into a structured GitHub Issue. A GitHub Issue is a shared record of a bug, task, or request.
A command for creating software architecture plans, technology choices, and design decisions from a feature description. It presents system structure, layers, recommended technologies, and design patterns.
A command that reads an issue-splitting plan and creates the related GitHub issues in bulk. GitHub issues are project tasks or reports, and a parent issue groups the smaller tasks needed for a larger feature.
An issue-improvement command that examines a GitHub Issue, asks questions about missing details, and updates its description. An Issue is a tracked request such as a feature, bug fix, documentation change, or refactoring task.
A command that breaks a large feature into implementable project issues and maps their dependencies. It favors vertical slices, where each issue includes the user interface, server code, database work, and tests needed for a usable part.
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.