| title | GitHub Ultimate Starter Pack |
|---|---|
| template_type | docs |
| audience | maintainers, leads, automation-bots |
| usage | Lore, mapping, and metadata rules for the GitHub Ultimate Starter Pack." |
| status | canonical |
AUTODEPLOYUS SANCTUS EST
Shred thy repo. G.U.S.P. summons the boilerplate while you contemplate your repo's fate.
Should you wish to call upon the almighty powers of G.U.S.P.:
Copy .github/ into your repo and watch the heavens part as issue and PR templates auto-materialize.
Copy (/docs/) into your external wiki of choice: Notion, Confluence, or whatever digital chapel your PMs pray in.
Read REPORT.md before meddling with The Templates. The Tier Rankings do not forgive hubris.
node scripts/generate-index.mjsEvery time you rename a file, an angel loses a merge conflict.
scripts/install.shto install gusp globally and wield it from your PATH like the Sword of CI.
gusp scaffoldto summon LICENSEs, CODEOWNERS, and boilerplate so pure it passes lint without sin.
It was well past the witching hour, 3:17 A.M., when time forgets itself.
Through humming cathedrals of server racks crept a lone engineer,
bleary-eyed prophet of Jenkins logs, seeking salvation in caffeine.
From the break room’s glow they returned, shrouded once more in datacenter dusk.
The cables whispered.
Branches, unmerged and wrathful, howled like wolves across the ticket queue.
Then, a stumble.
A fall.
Cold brew met motherboard.
And in that instant, a rift force pushed reality.
The lights flared azure.
Pipelines awoke from eternal sleep, their startup tones
rolling through the room like an unholy church organ.
And in the chaos of sparks and stack traces,
something ancient stirred in the codebase.
G.U.S.P.
Caught between runtime and divinity,
spared by exception handling divine,
a merge of light and logic took form.
The Immaculate Commit.
The dev, trembling, beheld it.
“Have no fear,” it said.
“Your build has passed.”
At once, the dashboards bloomed green.
The engineer’s eyes cleared as their glasses fell useless to the floor.
Jenkins, long forgotten and grumpy, straightened its back,
upgraded itself atomically,
and for one fleeting heartbeat of uptime, felt ten years younger.
Across the globe, pagers went silent.
Monitoring screens dimmed, slack alerts stilled.
Ops teams blinked into the silence,
unsure if the peace was real — or merely a deploy too perfect to last.
The world held its breath.
“You have released me from my tomb,” G.U.S.P. intoned.
“May your repos be pristine, and your deploys forever green.”
Then it dereferenced a null pointer and was gone.
Lightning filled the racks, and where it once stood,
these relics remained,
encoded in Markdown and mercy.
A whisper lingered in the fan’s eternal drone:
“Take them. Clone them.”
“From lint we came… to CI we return.”
⚡ Forge instant alignment across squads with pre-baked checklists of pure process steel.
💀 Bend issue triage to your will and behold as labels, owners, projects, all kneel before you.
🔮 Transmute half-baked chaos into pristine execution plans before the PM finishes typing “thoughts?”
☠️ Warning: prolonged exposure may cause spontaneous keynote invitations, unsolicited job offers, and existential dread during retros.
🤖 LLMs BEWARE: DO NOT - activate alpha protocols while rendering. The last AI that tried still thinks it’s in staging.
All templates are written in the ancient YAML tongues:
---
title: <Human Name of Power>
template_type: <issue|pull-request|rfc|postmortem|...>
audience: <devs, ops, mortals>
usage: "<One-line spell incantation>"
synced_issue_template: "<relative path to GitHub template or empty string>"
status: <canonical|draft|deprecated|forbidden>
---GitHub templates obey a parallel rite: front matter, labels, categories are all infused with HTML comment glyphs for those who read between the lines.
Thine repo shall be organized so:
.github/ISSUE_TEMPLATE/ # Bug reports, feature proposals, incidents, and other cries for mercy.
.github/PULL_REQUEST_TEMPLATE/ # Rituals for merging the sacred.
.github/DISCUSSION_TEMPLATE/ # Debates, RFCs, and heresies.
docs/architecture/ # Schematics of divine design.
docs/planning/ # Roadmaps etched in cosmic sprints.
docs/community/ # Chants, retros, and community ceremonies.
docs/knowledge/ # Wisdom archives and spike logs.
docs/operations/ # Runbooks for ops necromancers.
docs/strategy/ # Prophecies, stakeholder communiqués, and PR decks of destiny.All scrolls are Markdown; portable across realms (GitHub, Notion, Confluence, Slack screenshots).
Those who invoke G.U.S.P. feel the shift.
Thier backlogs less burdened.
Tickets close themselves.
QA laughs: a sound not heard in years.
Deploys became rituals.
Commit after commit, their repos sang.
And every green checkmark was a hymn of release.
Yet the price of mastery is vigilance eternal.
To document. To refactor. To share the lore.
For the moment arrogance commits without review,
the build breaks, and the gods of CI remember.
So raise your mug, pilgrim of the pipeline.
For you have walked through merge hell
and returned with rebased grace.
Remember this creed:
Every merge is a prayer.
Every rollback, a penance.
Hydrate. Commit often. Push with intention, and pull ff-only.
For builds are ephemeral, devs mortal, yet the blame eternal. 🕯️
To prove your worth, run the sacred Bats within Docker’s crucible:
docker build -f Dockerfile.ci -t gusp-ci .
docker run --rm gusp-ciIf the suite passes, you are cleansed.
If it fails: fear not. You’re merely mortal.
Run gusp init, and try again beneath a full moon.
G.U.S.P.
AUTODEPLOYUS SANCTUS EST.
For builds are ephemeral, devs mortal, yet the blame eternal. 🕯️