mobiustripper42
Community@mobiustripper42
Git-based session, task, and release lifecycle skills for Claude coding windows: PR shipping, phase planning, retrospectives, and versioned production promotion.
Agent Skills by mobiustripper42
Showing 7 vetted skills indexed across 1 GitHub repositories.
mobiustripper42bump-major
Bumps the major version in package.json, updates CHANGELOG.md, and tags the release on main.
mobiustripper42kill-this
Ships one task by committing code, running reviews, opening a PR, and logging the session.
mobiustripper42its-dead
Closes a session file by stamping end time, tallying points, and pushing the sessions branch.
mobiustripper42promote-production
Promote the main trunk to the production branch via fast-forward merge with version tagging.
mobiustripper42start-phase
Creates GitHub Issues from PROJECT_PLAN.md phase tasks and writes issue links back.
mobiustripper42its-alive
Initializes a development session by stamping time, opening a session file on an orphan git branch, and presenting a project briefing.
mobiustripper42retro
Closes project phases by computing throughput metrics from GitHub issues and writing retrospectives.
Frequently Asked Questions About mobiustripper42
FAQPage SchemaWhat tasks can I run with mobiustripper42's skills?▼
You can start and end tracked coding sessions, ship per-task PRs with build checks and code review, bump major versions with CHANGELOG entries, promote main to production via fast-forward merge, convert PROJECT_PLAN.md phases into labeled GitHub Issues, and run phase retrospectives with velocity math.
Who are these skills designed for?▼
Developers running structured, multi-task Claude coding sessions on versioned projects. They suit engineers who track work in PROJECT_PLAN.md and GitHub Issues, use trunk-based development on main, and want per-task PRs, session logs, and phase retrospectives with points-based velocity tracking.
What is the practical runtime workflow?▼
Start with /its-alive to open a session file and get a briefing, run /kill-this per task to ship PRs, then /its-dead once to close the session. At phase boundaries, /retro computes velocity and closes the phase, optionally chaining into /start-phase to create the next phase's GitHub Issues.
What prerequisites and dependencies are required?▼
A git repository with an active main trunk, an origin/production branch for releases, and a package.json with a version field for versioned projects. Phase planning requires PROJECT_PLAN.md with task rows; velocity math requires GitHub Issues carrying points:N labels and closedAt dates.
How do versioning and releases work across the skills?▼
bump-major handles breaking-change major bumps with CHANGELOG entries and tags on main. promote-production patch-bumps and tags the trunk, then fast-forwards production to it. retro owns patch bumps per merged PR and the phase-close minor bump on dev projects.