因為，出於神的話，沒有一句不帶能力的。 路加福音 1:37
For with God nothing shall be impossible. Luke 1:37
Every PR is a PrayRequest. 合併之前，先讀一段。
A GitHub bot that comments a context-matched Bible verse on every Pull Request — verse and reference, nothing else. The bot offers scripture and steps back; readers project their own meaning onto it.
PrayRequest reads the PR's title, description, diff size, and recent commits, asks Claude Haiku 4.5 for a verse that fits the change, and posts it as a comment. If the model is unavailable it falls back to a curated keyword matcher — the same table drives that fallback and shows the kind of mapping to expect:
| PR pattern | Verse reference | Vibe |
|---|---|---|
hotfix: / urgent / critical |
阿摩司書 9:11 | repair the broken walls |
refactor: or 500+ lines / 20+ files |
啟示錄 21:5 | behold, I make all things new |
feat: / new feature |
創世記 1:3 | let there be light |
security / auth / admin paths |
以弗所書 6:11 | put on the full armour of God |
fix: / bug / patch |
使徒行傳 3:19 | repent and turn back |
revert: / rollback |
列王紀下 19:15 | return the way you came |
todo / fixme / hack |
馬太福音 7:26 | build house on sand |
test: / spec |
雅各書 1:3 | testing of your faith |
docs: / readme |
申命記 5:22 | written on two stone tablets |
| (no match) | 馬太福音 21:22 | have faith in prayer |
Full mapping in
.github/prayrequest-verses.json —
20 entries plus a default fallback. The matcher walks the file in
order; first matching tag wins.
Scripture quotes are intended to use public-domain translations: Chinese Union Version (和合本, 1919) for Traditional Chinese and the King James Version (1611/1769) for English. Please verify copyright status and any attribution requirements for your jurisdiction before deploying.
A hotfix: PR gets (every comment is bilingual — 和合本 + KJV):
在那日，我必重建大衛倒塌的帳幕，修補其中的缺口⋯⋯ — 阿摩司書 9:11
In that day will I raise up the tabernacle of David that is fallen, and close up the breaches thereof⋯ — Amos 9:11
— 🙏 PrayRequest
A 500+ line refactor: PR gets:
那位坐在寶座上的說：「看哪，我把一切都更新了！」⋯⋯ — 啟示錄 21:5
And he that sat upon the throne said, Behold, I make all things new⋯ — Revelation 21:5
— 🙏 PrayRequest
Real reasons teams put a verse on a PR — beyond "it's funny":
- A pre-merge pause. One non-functional line that doesn't summarize the diff, doesn't gate the merge, doesn't ping a reviewer. It just lives there. In teams where merge velocity is the only metric, a small ambient interruption is its own value.
- Risk acknowledgment without finger-pointing. A
hotfixverse is a softer "are you sure?" than a red banner. The author and reviewer both read it; nobody has to type the word "YOLO" out loud. - Canonizing recurring memes. Friday-night hotfixes, "I'll add tests later," 3,000-line refactors — these vibes recur but otherwise leave no artifact. The bot turns the meme into a durable thing in the PR timeline that future-you can scroll back through.
- Cross-language team rituals. Bilingual Chinese-English teams find 「合併之前，先讀一段」 lands as an in-joke that survives translation in a way English-only humor doesn't.
- Blameless callouts. "PR touches
auth/middleware.ts" plus 以弗所書 6:11 communicates the same thing as a bluntly-worded reviewer comment, but without singling anyone out. The verse is the medium; the targeting is implicit. - Onboarding signal. New engineers learn which kinds of PRs the team treats as risky by noticing which verses keep showing up. The bot is a slow, ambient style guide.
When not to use:
- Repos where any religious reference would land badly. v3 plans alternate quote sources (Tao Te Ching, Sun Tzu, Shakespeare). Until then, opt-in only — never deploy to someone else's repo without asking.
- Bot-authored PRs (Dependabot, Renovate). Already auto-skipped.
- Solo repos where there's no audience for the joke.
PrayRequest is a hosted GitHub App. Install once at the org or user
level — no workflow file in your repo — and summon in any PR thread
with @prayrequest. The display name keeps "PrayRequest" casing; the
@-mention slug is lowercased per GitHub convention as
@prayrequest[bot].
Currently shipped (v1). Cloudflare Workers + TypeScript. Auto-bless
fires when @prayrequest is in the PR title or body. @prayrequest
in any PR comment summons. @prayrequest reroll picks an alternate.
Verse selection is LLM-driven (Claude Haiku 4.5 via the Cloudflare
Workers AI binding), with the curated keyword matcher as a fallback.
Setup and deploy: app/README.md.
Full roadmap and design rationale: docs/plan.md.
YOLO PRs — Friday 6pm hotfixes, no-test merges, 3,000-line refactors, "I'll add tests later" — are a recurring team meme but leave no artifact. PrayRequest canonizes the vibe.
The verse-only format is intentional. The bot offers scripture and gets out of the way. Whether the reader takes it as prayer, joke, omen, or noise is up to them — and that ambiguity is the design.