$npx -y skills add jmstar85/oh-my-githubcopilot --skill verifyVerify that a change really works before claiming completion. Activate when user says: verify this, check if it works, prove it works.
| 1 | # Verify |
| 2 | |
| 3 | Turn vague "it should work" claims into concrete evidence. |
| 4 | |
| 5 | ## Workflow |
| 6 | 1. Identify the exact behavior that must be proven |
| 7 | 2. Prefer existing tests first |
| 8 | 3. If coverage is missing, run narrowest direct verification commands |
| 9 | 4. If direct automation not enough, describe manual validation steps |
| 10 | 5. Report only what was actually verified |
| 11 | |
| 12 | ## Verification Order |
| 13 | 1. Existing tests |
| 14 | 2. Typecheck / build |
| 15 | 3. Narrow direct command checks |
| 16 | 4. Manual or interactive validation |
| 17 | |
| 18 | ## Rules |
| 19 | - Do not say a change is complete without evidence |
| 20 | - If a check fails, include the failure clearly |
| 21 | - If no realistic verification path exists, say so explicitly |
| 22 | - Prefer concise evidence summaries over noisy logs |
| 23 | |
| 24 | ## Output |
| 25 | - What was verified |
| 26 | - Which commands/tests were run |
| 27 | - What passed |
| 28 | - What failed or remains unverified |