0 Fork 0

mirror of https://github.com/kevinveenbirkenbach/computer-playbook.git synced 2026-11-12 05:36:40 +00:00

Files

T

kevinveenbirkenbach 375119b414 docs(agents): clarify push/PR flow, target repo, run-id resolve

- pull-request.md: PRs must target canonical repo behind s.infinito.nexus/code; agent resolves redirect and compares against origin.
- push-trigger-pull.md: freeze <branch> once (propose current and wait if unnamed); forbid checkout/switch; handle non-fast-forward; fetch before diff; define distro-specific scope; capture <prev-run-id> to avoid stale-run watch; resolve <pr-number> via isDraft dispatch; null-guard.
- cheatsheet.md: push-trigger-pull prompt takes explicit <branch> placeholder.

2026-04-17 22:54:13 +02:00

7.3 KiB

Raw Blame History

Cheatsheet 📋

Copy-paste prompt templates the operator can hand to an agent to kick off a workflow. Each prompt routes the agent to its authoritative procedure file; this page is a navigational aid only and MUST NOT be treated as source of truth.

Replace every <placeholder> before sending.

Every prompt below instructs the agent to first clarify all open requirements through active listening, then act autonomously through to completion with as few follow-up questions as possible.

Selection Matrix 🧭

Situation	Use
Building a new feature, app, or larger change	Development
Fixing or evolving a single web app role with the deploy/test loop	Web Development Iteration
Running or validating tests for a specific scope	Testing
Cleaning up code, docs, or roles after a change	Refactor and Optimize
A GitHub Actions / CI run failed and needs triage	Pipeline Debugging
A local deploy is failing on the host	Local Deploy Debugging
Operator placed a `.log` or `job-logs.txt` file in the workdir for ad-hoc inspection	Log File Inspection
Staged changes are ready to be committed	Commit
A branch is ready to be opened as a pull request	Pull Request Creation
A branch needs to be pushed, validated via manual CI, and transitioned through the draft → ready-for-review cycle	Push, Trigger, Pull
A new requirement needs to be written	Requirement Creation
An existing requirement file needs to be implemented end to end	Requirement Implementation

Development 🧱

For any change with a documented acceptance scope, Requirement Implementation is the preferred entry point; use this prompt only when no requirement file exists or applies.

Follow the instructions from AGENTS.md, develop <feature-or-app> by following the procedure in docs/agents/action/develop.md. Begin by clarifying every open requirement through active listening, then act autonomously through to completion with as few follow-up questions as possible. Use mode /caveman ultra.

SPOT: develop.md

Web Development Iteration 🔁

For any change with a documented acceptance scope, Requirement Implementation is the preferred entry point; use this prompt only when no requirement file exists or applies.

Follow the instructions from AGENTS.md, iterate on web app role <role> by following the procedure in docs/agents/action/iteration.md. Begin by clarifying every open requirement through active listening, then act autonomously through to completion with as few follow-up questions as possible. Use mode /caveman ultra.

SPOT: iteration.md

Testing ✅

Follow the instructions from AGENTS.md, run and validate tests for <scope> by following the procedure in docs/agents/action/testing.md. Begin by clarifying every open requirement through active listening, then act autonomously through to completion with as few follow-up questions as possible. Use mode /caveman ultra.

SPOT: testing.md

Refactor and Optimize ♻️

Follow the instructions from AGENTS.md, refactor and optimize the affected files by following the procedure in docs/agents/action/refactor.md. Begin by clarifying every open requirement through active listening, then act autonomously through to completion with as few follow-up questions as possible. Use mode /caveman ultra.

SPOT: refactor.md

Pipeline Debugging 🛠️

Follow the instructions from AGENTS.md, triage the failing CI run at <github-actions-run-url> by following the procedure in docs/agents/action/debug/pipeline.md. Begin by clarifying every open requirement through active listening, then act autonomously through to completion with as few follow-up questions as possible. Use mode /caveman ultra.

SPOT: pipeline.md

Local Deploy Debugging 🧰

Follow the instructions from AGENTS.md, debug the failing local deploy of role <role> by following the procedure in docs/agents/action/debug/local.md. Begin by clarifying every open requirement through active listening, then act autonomously through to completion with as few follow-up questions as possible. Use mode /caveman ultra.

SPOT: local.md

Log File Inspection 🔍

Follow the instructions from AGENTS.md, inspect the log file <path-to-log> by following the procedure in docs/agents/action/debug/log.md. Begin by clarifying every open requirement through active listening, then act autonomously through to completion with as few follow-up questions as possible. Use mode /caveman ultra.

SPOT: log.md

Commit 💾

Follow the instructions from AGENTS.md, commit the staged changes by following the procedure in docs/agents/action/commit.md. Begin by clarifying every open requirement through active listening, then act autonomously through to completion with as few follow-up questions as possible. Use mode /caveman ultra.

SPOT: commit.md

Pull Request Creation 📤

Follow the instructions from AGENTS.md, open a pull request for the current branch by following the procedure in docs/agents/action/pull-request.md. Begin by clarifying every open requirement through active listening, then act autonomously through to completion with as few follow-up questions as possible. Use mode /caveman ultra.

SPOT: pull-request.md

Push, Trigger, Pull 📡

Follow the instructions from AGENTS.md, push branch <branch>, run it through the manual-CI draft cycle, and transition the PR to ready-for-review by following the procedure in docs/agents/action/push-trigger-pull.md. Begin by clarifying every open requirement through active listening, then act autonomously through to completion with as few follow-up questions as possible. Use mode /caveman ultra.

SPOT: push-trigger-pull.md

Requirement Creation ✍️

Follow the instructions from AGENTS.md, create a new requirement for <topic> by following the procedure in docs/contributing/requirements.md. Begin by clarifying every open requirement through active listening, then act autonomously through to completion with as few follow-up questions as possible. Use mode /caveman ultra.

SPOT: requirements.md

Requirement Implementation 🚀

If no requirement file exists yet for the work, run Requirement Creation first to produce one.

Follow the instructions from AGENTS.md, implement requirement docs/requirements/<NNN-topic>.md by following the procedure in docs/agents/action/requirements.md. Begin by clarifying every open requirement through active listening, then act autonomously through to completion with as few follow-up questions as possible. Use mode /caveman ultra.