ci-check
01Command Claude Code
Diagnose the most recent failed CI run on the current branch and emit a deterministic repro packet.
Rebel: open-source agentic AI desktop app. Public mirror — source of truth is internal; published one-way via CI.
This repository also configures its own agents. See what rebel-app tells them →
Command Claude Code
Diagnose the most recent failed CI run on the current branch and emit a deterministic repro packet.
Command Claude Code
Ask the user: "What problem or question would you like the two researchers to investigate?".
Command Claude Code
Finish a Rebel-handed-off task — notify Rebel and exit cleanly so the SessionEnd hook fires.
Command Claude Code
Safely sync local branch with origin — fetches, merges, advances submodules, validates, and pushes everything in the right order.
Command Claude Code
Triple-review a merge/rebase to verify nothing was lost and conflicts were handled correctly.
Command Claude Code
Promote a beta-certified SHA to production by fast-forwarding main to it (auto-triggers the stable release.yml build).
Command Claude Code
Read the cloud VM setup guide at docs/research/260507clouddroidvmsetup.md and walk the user through the provisioning process.
Command Claude Code
Full production release workflow - changelog update, doc sync, submodule push, version bump, merge to main, validation.
Command Claude Code
Launch all 7 reviewers in parallel to review code changes from this conversation.
Command Claude Code
Launch all 7 reviewers in parallel to evaluate a plan before implementation.
Command Claude Code
Start a task — find or create a Linear ticket, move it to In Progress, and begin work.
Command Claude Code
Trigger the CI UI smoke test workflow with an optional custom test prompt.
Command Claude Code
Restart the dev server and open Rebel with a new or existing conversation to integration-test your changes before committing.
Command Claude Code
Launch the Electron app via MCP and test UI changes by clicking around and verifying behavior.
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: