GitAlive ⚡ — the repo-page journey gets a name worthy of it (presentation → gitalive)#26
Merged
Merged
Conversation
…fter BREAKING: /lazarus:presentation → /lazarus:gitalive, /lazarus:presentation-repair → /lazarus:gitalive-repair. Artifacts: GITALIVE_AUDIT.md / GITALIVE_CHANGES.md / .lazarus/gitalive-waivers.yml. gitalive-repair accepts a legacy PRESENTATION_AUDIT.md so v0.6/v0.7 audits still execute. Why: 'presentation' was abstract (could mean slides) and 'make it presentable' didn't say what 'it' was. GitAlive (Larry's coinage) rides the resurrection theme — the repo page is the project's proof of life. The love: dedicated README spotlight section with a before/after SVG built from the real dogfood findings (name-in-a-PNG, badge-less CI, no-ToC, stale docs → all green), ToC entry, new Just-shipped note. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Rename + spotlight. The newest journey had the weakest name:
presentationwas abstract (slides?), and user feedback ("make what presentable?") confirmed it. New name — GitAlive (the maintainer's coinage, riding the Lazarus resurrection theme): the repo page is your project's proof of life.Breaking changes (called out plainly)
/lazarus:presentation/lazarus:gitalive/lazarus:presentation-repair/lazarus:gitalive-repairPRESENTATION_AUDIT.md/PRESENTATION_CHANGES.mdGITALIVE_AUDIT.md/GITALIVE_CHANGES.md.lazarus/presentation-waivers.yml.lazarus/gitalive-waivers.ymlMitigation:
gitalive-repairexplicitly accepts a legacyPRESENTATION_AUDIT.md, so audits produced in the two days the old names existed still execute. Window of exposure: v0.6.0/v0.7.0 only.The love
assets/gitalive-before-after.svg) built from the real dogfood findings: name trapped in a PNG / badge-less CI / no ToC / stale docs → real H1 / live badge / ToC / clean re-audit. Alt-texted, ToC-linked.Verified
claude plugin validate✔; isolated-HOME install: both renamed skills + support files register (6 core skills).name:frontmatter rule held for both; nolazarus-prefix (the /lazarus:lazarus-x trap).🤖 Generated with Claude Code