mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-09 20:26:33 +00:00
kevinveenbirkenbachandClaude Opus 5
bac30b76fa
Four independent findings, each at its root. sys-svc-container: tasks/00_core/gpu.yml included 'nvidia.yml' by bare name, but the role is entered through tasks_from: 00_core.yml, so a relative include resolves against tasks/ instead of next to the including file. Every sibling include in 00_core.yml already carries the 00_core/ prefix. web-app-seaweedfs:c61b29bd16made services.seaweedfs.enabled and .shared literal and stated that the variant pin follows, but never touched meta/variants.yml. Both variants still repeated that literal, which variants-static-override counts as four offenders. They set exactly what the base declares, so they go. The base keeps the literal and regains the dynamic-flag marker the console split dropped ate8e89d293d: the flag's only job is joining the engine's shared_net, and its false branch yields a console container that cannot start, which the lint names as a legitimate exception. docs: the i8-tuner skill landed without its cheatsheet row, which the skills coverage guard reads as a missing skill. The remaining three files are that pass's own formatter output: quote normalisation in nvidia.yml and line wrapping in two test files. Not covered here: the two hallucinated URLs in locale/ko/LC_MESSAGES/docs.po, because a translation run is writing the catalogs. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
47 lines
2.9 KiB
Markdown
47 lines
2.9 KiB
Markdown
# 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` |
|
|
| Bringing UI roles into the corporate design, role by role from the design queue | `i8-designer` |
|
|
| 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` |
|
|
| Making CI, a deploy or a gate faster without giving up coverage | `i8-tuner` |
|
|
| Checking a branch out into a parallel worktree | `i8-worktree-create` |
|
|
| Releasing a parallel worktree and its slot | `i8-worktree-down` |
|
|
| Freeing disk space and `/tmp` that agents filled | `i8-cleanup` |
|
|
| 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` |
|
|
| Leading a CI run with a priority line that verifies the branch's open questions | `i8-ci-trigger-priority` |
|
|
| Verifying from both ends at once: the CI run on a triage loop plus local iteration | `i8-verify-parallel` |
|
|
| Writing the blog article, banner image and social posts for a release | `i8-release-article` |
|
|
| Writing a new requirement | `i8-requirement-create` |
|
|
| Implementing an existing requirement file end to end | `i8-requirement-implement` |
|