commit-agora
01Command
A commit workflow for the Agora project that checks quality, commits a feature branch, and opens a pull request to the dev-1.0.0 branch.
The digital town square where AI agents (PM/Architect/Coder/Tester) collaborate via group chat, while the human acts as the sole Leader. Built with TypeScript + DeepSeek Harness, featuring true parallel execution, cooperative preemption, MCP tools, and git worktree isolation.
Command
A commit workflow for the Agora project that checks quality, commits a feature branch, and opens a pull request to the dev-1.0.0 branch.
Command
A command that runs a specified task ID, such as 0.4, through the EPCC-V development process.
Command
A command for explaining code, architecture choices, and design concepts using documentation from an Agora project. It traces explanations back to the original document text.
Command
A session-start command for the Agora workflow. It reads the project rules, finds current progress, fixes the specification context, and waits for confirmation before work begins.
Command
A command that finds the next task marked ready and runs it through the EPCC-V development process.
Command
Post-merge commands for finishing a task after its pull request has been merged. They synchronize the dev-1.0.0 branch, mark the task done, update related tasks, and check whether the work stage is complete.
Command
A command for reviewing a pull request’s architecture and handling its comments, with output in Chinese. A pull request is a proposed code change submitted for review before merging it into a project.
Command
A command for reading and summarizing the specification for the current task. A specification document records the original constraints and architecture rules.
Command
A command for retrying a task that failed or stopped, continuing from its last saved point.
Command
A command that quickly shows the current status of the Agora project, including its stage, tasks, progress, and milestones.
Command
A command that updates affected project documentation after recent decisions or code changes. Its purpose is to prevent the written specification from drifting away from the project.
Command
A command for running integration tests progressively from Phase 0 through later phases, including cross-phase checks and a full unit-test regression. Integration tests check whether multiple parts work together.
Command
A command for integration testing during the current development phase. Integration tests check how multiple parts of a system work together.
Command
A command that builds and runs the unit tests related to the current task, then reports and examines failures.