Start with the consequences
What happens if this breaks?
For a disposable personal app, describe what you want, try it, and keep chatting. As people depend on the result, add checks that protect their time, data, and trust. Shaka is for the point where a change deserves a tested, reviewed pull request.
Just for me
I can recreate it.
A disposable personal experiment
Chat, try it, iterate. You do not need pull requests or a test suite yet.
Friends or coworkers
Others lose time.
A shared tool with saved work
Check important user journeys, protect saved data, and have a recovery path.
Customers depend on it
Failures damage trust.
An application people rely on
Automate critical checks. Add targeted review, monitoring, and rollback.
Critical service
Minutes cause major losses.
An outage can cost thousands a minute
Set reliability targets. Stage releases, test failures, and practice recovery.
Illustrative situations, not mandatory levels. A five-person payroll tool can need stronger safeguards than a popular disposable toy. Data sensitivity, recovery difficulty, and the change itself matter as much as audience size.
Why use it
The hard part isn't the code. It's knowing what was checked.
An agent hands you something plausible, and you are left reconstructing what it read, what it ran, and what that proves. Shaka makes those answers part of the pull request.
Spend less time directing the process
Describe the outcome. Shaka supplies the steps through testing, review, and PR delivery.
Avoid unnecessary CI runs
Tests and adversarial reviews run locally, with before-and-after screenshots for UI changes, so problems are fixed before the push.
Make review easier
The PR leads with the result and evidence. A code walkthrough explains the implementation choices.
See what a PR cost
Token usage and estimated dollar cost, including local review, appear in the PR. Missing usage is marked unknown.
Control merging
Choose Ask to merge on GitHub yourself, or Auto to let the agent merge after checks and required approvals.
Resume unfinished work
WIP Details on the PR name the owning agent chat, where it stopped, and what comes next.
How it works
One workflow, your repository's commands.
A shared workflow
One skill guides each task through planning, implementation, verification, review, and delivery. Your repository settings supply the commands and merge preference.
Evidence before delivery
Tests, independent review, and visual comparisons help you judge the result before you merge.
PR verification →Explicit enforcement
Ruby helpers check configuration, filter public comments, and enforce merge conditions alongside GitHub. The workflow reference shows which steps rely on the agent.
What is enforced →Start with one task.
Shaka needs Ruby 3.4 or later, Git, an authenticated GitHub CLI, and a coding agent that can load skills and run commands. The getting-started guide gives you prompts for installing Shaka and configuring your repository.