passlisted

# pass The pass is where the chef inspects every plate before the runner carries it out. Nothing leaves half-cooked, mislabeled, or with a thumbprint on the rim. This skill is that inspection for a pull request: the gate between "the code works on my machine" and "this is in front of a reviewer." The PR is not filed until it clears the pass. A PR is a request for someone else's time. The bar is not "it compiles," it is "a reviewer can understand it, trust it, and merge it without doing the work you skipped." ## The checklist Run every check. Anything that fails holds the plate: tell the author which check failed and why, fix it, then re-run the pass. Do not file and do not silently start fixing without surfacing the hold first. The sub-skills below are the preferred way to satisfy a check. If a referenced skill is not installed, perform its equivalent by hand, the gate still holds; the skill is the shortcut, not the requirement. Likewise `gh` assumes GitHub: on another platform, draft the artifacts and hand them to the author to file through their flow. "Non-trivial" here means anything beyond a one-line, obviously-safe change (a dependency bump, a typo, a constant tweak). A small-looking change that touches behavior, like the timeout bump in the example below, is not trivial. ### 1. It is a real fix, not a bandaid The change addresses the root cause, not the symptom. If it is a bugfix, you reproduced the bug, traced it to its source, and the fix targets that source. A