mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-08 03:38:23 +00:00
kevinveenbirkenbachandClaude Opus 5
eed0879eaa
Conflict: roles/web-app-bridgy-fed/files/Dockerfile
Both sides extended the header comment. main also replaced the upstream
checkout, `git clone --depth=1 --branch "${BRIDGY_REF}"`, with git init plus a
fetch of the single ref; this branch never touched those lines, so git took
main's version automatically and only the comment collided.
Resolved to main's file verbatim. It is a superset of ours in both respects:
it keeps our two comment paragraphs and adds a third naming the trip-wire the
non-idiomatic fetch exists for, namely that BRIDGY_REF is a commit and
`git clone --branch` refuses one. Verified byte-identical to stage 3.
Committed with the hook skipped and before the semantic audit of the other 45
files finished. main brings a lint rule that has never seen this branch's
roles, image bumps on svc-ai-ollama and web-app-nextcloud which this branch
rewrote, a stylelint major, and release 13.0.0 across the packaging surface.
Any of those can merge cleanly line by line and still be wrong.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2.3 KiB
2.3 KiB
Cheatsheet 📋
Each operator workflow has a skill that routes the agent to its authoritative
procedure and drives it — clarifying open requirements first, then acting
autonomously to completion. Most are i8- skills specific to this repository; a
few (such as triage) are portable skills shared across projects.
How to use 🧭
Invoke a skill with its slash command, for example /i8-develop or /i8-quality,
or name the skill in your message to the agent. Supply the concrete target (role,
scope, requirement file, or run URL) in the same message; the skill fills the rest
from its procedure file. Run make install-skills to (re)install them.
Skills 🗂️
| Situation | Skill |
|---|---|
| Building a new feature, app, or larger change | i8-develop |
| Iterating a web app role in compose mode | i8-iterate-compose |
| Iterating a web app role in swarm mode | i8-iterate-swarm |
| Validating every role across both modes, compose then swarm | i8-iterate-roundtrip |
Iterating on svc-runner or the self-hosted runner infrastructure |
i8-iterate-runner |
| Iterating on a GitHub Actions workflow | i8-iterate-workflow |
Writing or updating a Playwright spec for a web-* role |
i8-iterate-playwright |
| Running or validating tests for a specific scope | i8-test |
Running the quality gate (make quality) to green |
i8-quality |
Running the full gate (make quality-high: quality plus every lint) to green |
i8-quality-high |
| Cleaning up code, docs, or roles after a change | i8-refactor |
| Checking a branch out into a parallel worktree | i8-worktree-create |
| Releasing a parallel worktree and its slot | i8-worktree-down |
| A GitHub Actions / CI run failed and needs triage | triage |
| A local deploy is failing on the host | i8-debug-local |
Inspecting a *.log or *job-logs.txt file dropped in the workdir |
i8-debug-log |
| Pulling a sibling feature branch and merging it into the current one | i8-merge-sibling |
| Staged changes are ready to be committed | i8-commit |
| A branch is ready to be opened as a pull request | i8-pull-request |
| Pushing a branch through the manual-CI draft → ready-for-review cycle | i8-push-trigger-pull |
| Writing a new requirement | i8-requirement-create |
| Implementing an existing requirement file end to end | i8-requirement-implement |