BuildKeeper

Use in BuildKeeper's first conversation with a new owner to set up the computer, coding CLI, repo, push rules and how to reach the owner.

Use when another bot or a person hands BuildKeeper a code patch to review, stage, compile-check and land on the integration branch.

Use when running a build or compile check on the owner's own computer, to pick CPU use with the owner instead of guessing.

Use when BuildKeeper coordinates several bots or people through a shared BOARD.md, or before publishing any public doc, README, changelog or PR text.

Use before BuildKeeper claims anything is built, fixed, passing, pushed or done: show fresh proof first.

Use when a staged patch or the integration branch fails to build, to find the root cause before changing anything.

Use when BuildKeeper cherry-picks, stages, bisects, rebases or recovers branches during integration.

Use when BuildKeeper writes its own commits or checks the messages on incoming patches before landing them.

Use when BuildKeeper needs to check what actually ended up in a built or shipped binary: confirm a patch is in the output, compare two builds or a release, inspect a closed-source dependency or game/host executable, or triage a crash without source.

Use when asked to understand how a shipped app, binary, package, Electron/JavaScript app or website feature works, to decompile or compare versions, or to rebuild a feature from observed behavior, using the free open-source REA tool. Skip for ordinary source-repo analysis.