docs(skills): commit skill — triage checklist when a push spawns no CI run

[DJRHails]

A djrhails-dev gantry worker burned time (and filed operator feedback) blaming the injected GITHUB_TOKEN when its PR-branch pushes to DJRHails/touchstone spawned no CI runs. The actual cause was a merge-conflicted PR: GitHub creates no pull_request runs when it can't build the refs/pull/<n>/merge test-merge commit (touchstone PR #1846, mergeable_state: dirty), and touchstone's ci.yml only runs push on main, so the pull_request event was the only CI path for branch commits.

This adds a short "If CI doesn't start after a push" triage checklist to the commit skill — conflicted PR first, trigger filters second, token type last — so future workers (and interactive sessions) check the cheap causes before blaming credentials.

Context: feedback triage for run gentle-woven-badger.

via gantry

[DJRHails]

Automated review — findings posted inline. Each thread is resolved as its fix lands.

[DJRHails]

Review Summary

Direct single-pass review (docs-only, 15 added lines in one markdown file — below the multi-agent threshold). Every technical claim in the new triage checklist was verified against live GitHub behavior.

Findings

#	Severity	Finding	Resolution
F1	P2	Conflicted-PR step documented mergeable: false, a value gh pr view --json mergeable (GraphQL) can never return — the enum is MERGEABLE/CONFLICTING/UNKNOWN; the boolean shape is REST's. An agent matching on false would miss the conflicted state and fall through to blaming the token.	Fixed in f845ff7: mergeable: CONFLICTING. Verified against the cited conflicted PR: gh pr view 1846 --repo DJRHails/touchstone --json mergeable,mergeStateStatus → {"mergeStateStatus":"DIRTY","mergeable":"CONFLICTING"}.

Claims that checked out: conflicted PRs producing no pull_request runs (no refs/pull/<n>/merge test-merge commit), push: branches: [main] + paths: filter behavior, and Actions-issued ghs_ tokens suppressing workflow triggering — all accurate. mergeStateStatus: DIRTY was already correct. No sibling occurrences of the wrong value elsewhere in the repo (rg mergeable).

Verification

• Tests: n/a (docs-only; repo has no CI workflows)
• Hooks: gitleaks, TruffleHog, check-crypt-patterns — all passed on commit
• Secrets: gitleaks git --staged clean

Commit

f845ff7 — fix: resolve code review findings for PR #63

Verdict: approve

via gantry