PR Readiness & Verification FAQs

Question 1

What are the 'red flag' words to avoid?

Accepted Answer

Phrases like 'probably,' 'seems to,' 'should work,' or expressing satisfaction ('Great!', 'Done!') before running verification are flagged as process violations.

Question 2

Can this skill be used for build and lint checks?

Accepted Answer

Yes, it requires executing the full build or lint command and verifying an 'exit 0' status before allowing any claim that the code is clean or buildable.

Question 3

Why is 'should pass' not considered sufficient?

Accepted Answer

Qualitative claims lack empirical evidence. This skill mandates running fresh commands to prove functionality through raw logs and exit codes rather than assumptions.

Question 4

How does this skill handle regression testing?

Accepted Answer

It follows a strict red-green cycle: verifying a test fails when the fix is reverted and passes when the fix is applied, ensuring the test actually covers the bug.

Question 5

What happens if an agent reports success independently?

Accepted Answer

The skill prevents trusting agent reports at face value, requiring a manual check of the VCS diff and a fresh run of verification commands to confirm the state.

PR Readiness & Verification

Key Features

Use Cases

PR Readiness & Verification

Key Features

Use Cases