Base repository for Claude vibecoding
- Python 61.4%
- Shell 38.6%
ca1886f5d0
GitHub workflow runs can finish with conclusion "timed_out", which is equally actionable as "failure" or "action_required" but was silently ignored before. Add it to the failure conditions so clanker-prep triggers Claude when a run times out. Workflow authored by Maria Matejka <vibecoding@jmq.cz> Fixes #20 |
||
|---|---|---|
| .claude | ||
| .github/workflows | ||
| claude | ||
| docs | ||
| .claude-base-files | ||
| .gitignore | ||
| clanker-housekeeping | ||
| clanker-prep | ||
| clanker-run | ||
| clanker-setup | ||
| CLAUDE.md | ||
| LICENCE.md | ||
| README.md | ||
| setup-remotes | ||
Claude Base
This is my Claude-Code base repository for central housekeeping of my development rules. Feel free to suggest additions by filing issues or pull request.
For full documentation, setup guides, and project overview, see the claude-base website.
Expected workflow
There is a dedicated (virtual) machine running a clanker or a bunch of them. That machine should not have any write access anywhere outside itself, and should be regularly backed up.
The operator (myself) logs into the virtual machine whenever handy, pulls the git locally, does code review and merges, and pushes into public repo.
Initialization
- Merge this project into your project
- Clone your project into your clanker enclosure
- Setup needed tools:
./clanker-setup