markdownmegithub-worktreepublic

Keep the work reviewable.

Start the repo, explain the change, and write the changelog.7 focused tools for the handoffs around your code.

Write a README Write the PR

No signup
No repository access
Missing facts stay missing

example handoff · no repo connected

$ git status --short

M src/checkout.ts

?? tests/checkout.test.ts

$ git log -1 --pretty=%s

fix(checkout): prevent duplicate submits

handoff

Issue scoped. Tests named. Claim stays reviewable.

Repository workbench

Choose the next handoff.

These tools do not inspect GitHub. Paste only the context needed for the artifact you are making.

git init

Start the repository

Give the project a front door, clear contribution rules, and the files people look for first.

GH-01Runs locally

README Generator

Build a useful README with installation, usage, and project context—not a decorative wall of headings.

Bring: Project purpose and setup steps
Get: README.md

Open tool

GH-02Runs locally

License Generator

Choose a common open-source license and generate the complete repository file.

Bring: License choice, name, and year
Get: LICENSE

Open tool

GH-03Runs locally

CONTRIBUTING.md Generator

Set expectations for setup, code style, issue reporting, and the pull request process.

Bring: Your contribution workflow
Get: CONTRIBUTING.md

Open tool

GH-04Runs locally

Badge Generator

Create restrained shields.io badges with copy-ready Markdown for the repository header.

Bring: Label, status, color, and link
Get: Markdown badge

Open tool

git push -u

Ship the change

Make the history and review surface explain what changed, why it changed, and what was actually tested.

GH-08AI service

Conventional Commit Generator

Turn a real change summary into a conventional commit with a truthful release signal.

Bring: What changed and whether it breaks
Get: Commit message

Open tool

GH-09AI service

PR Description Generator

Draft a reviewer-ready summary, change list, test plan, and explicit follow-ups.

Bring: Intent, changes, and tests run
Get: Pull request body

Open tool

gh release create

Release and document

Translate the merged work into a durable project record and a useful explanation for the people affected.

GH-12Runs locally

Changelog Generator

Maintain a Keep a Changelog-style record across Added, Changed, Fixed, and Security sections.

Bring: Version and categorized changes
Get: CHANGELOG.md

Open tool

Repository truth > plausible prose

AI can format the handoff. It cannot know what happened.

Include the relevant behavior, constraints, commands, and test results. If a detail is absent, grounded tools should flag the gap—not turn it into a fact.

Write a grounded PR description

Ready for review

Give the next person the context you had.

Draft the handoff