The GitHub cycle
How one piece of work travels from an idea to merged code.
Every change cckit makes follows this same path. Read it left to right: an issue says what to do, a branch gives the work a private place to happen, the work becomes a pull request, and review either merges it or sends it back. cckit gives you one command for each step.
The steps
Section titled “The steps”-
Issue — a short note of one thing to do. It has a number (like
#42) that follows the work the whole way through. -
Branch — a private copy of the code to change, so your work never disturbs anyone else’s.
cckit start 42makes the branch and an isolated worktree for issue #42. -
Work — make the change. Run
bash scripts/check.sh(or your project’s checks) until it passes. -
Pull request — propose the change back to the main code.
cckit pr 42 "<summary>"opens it and links it to issue #42, so merging the request closes the issue. -
Review — automated checks run, and a person or an agent takes a look. If it’s good, it merges into
main. If not, it comes back as changes and you return to step 3.
The pull request carries its own proof
Section titled “The pull request carries its own proof”A pull request shouldn’t just claim the checks passed — it should show them. So when cckit opens a request it can attach the actual output as a comment: the build log, the typecheck log, a screenshot of the working screen. That’s the evidence on the request, and it’s what lets a reviewer (a person or an agent) trust step 5 without re-running everything by hand.
Each piece of evidence gets its own comment, named by its caption — one for build, one for
typecheck, one for a screenshot. Push again and cckit updates that same comment in place
rather than adding a second one, so a request that took ten pushes still shows one current build
log instead of ten stale ones.
Image evidence has one real limit: GitHub has no supported way to upload a file to a comment from the command line, so a screenshot is referenced by its path with instructions, not embedded. Drag it into the comment box yourself, or host the file and cckit will embed it.
The commands, in order
Section titled “The commands, in order”| Step | Command |
|---|---|
| Start the work | cckit start <issue> |
| Open the request | cckit pr <issue> "<summary>" |
| Close a no-op | cckit close <issue> "<reason>" |
| See the board | cckit sync |
| What’s next | cckit next |
Each command is explained in the CLI reference.
Independent, educational project — not affiliated with or endorsed by Anthropic. Claude and Claude Code are trademarks of Anthropic PBC.Disclaimer & trademarks ·
From Mexico withloveby josegtz