Name: summarize-branch
Author: zauberzeug

Prompt file imported from zauberzeug/lizard (.cursor/commands/summarize-branch.md). Copyright stays with the author.

Read README.md, AGENTS.md, and CONTRIBUTING.md, then write a precise and concise PR description. Lead with the motivation of the change, then explain what changed and design decisions made. Also mention special assumptions or risks implied by the changes.

The summary should be in a ```markdown code block, so the user can copy and paste it into the PR description. Ensure the summary length corresponds to the overall size of the PR (small PRs should be shorter than large PRs). Adhere to the following format:

### Motivation

<!-- What problem does this PR solve? Which new feature or improvement does it implement? -->
<!-- Please provide relevant links to corresponding issues and feature requests. -->

### Implementation

<!-- What is the concept behind the implementation? How does it work? -->
<!-- Include any important technical decisions or trade-offs made -->

### Progress

- [ ] I chose a meaningful title that completes the sentence: "If applied, this PR will..."
- [ ] The implementation is complete.
- [ ] Tested on target hardware (or not applicable).
- [ ] Documentation has been added (or is not necessary).

Also provide three suggestions for a PR title which completes the sentence "If applied, this PR will..."

Install summarize-branch and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "prompt": "Read README.md, AGENTS.md, and CONTRIBUTING.md, then write a precise and concise PR description.\nLead with the motivation of the change, then explain what changed and design decisions made.\nAlso mention special assumptions or risks implied by the changes.\n\nThe summary should be in a ```markdown code block, so the user can copy and paste it into the PR description.\nEnsure the summary length corresponds to the overall size of the PR (small PRs should be shorter than large PRs).\nAdhere to the following format:\n\n```markdown\n### Motivation\n\n\n\n\n### Implementation\n\n\n\n\n### Progress\n\n- [ ] I chose a meaningful title that completes the sentence: \"If applied, this PR will...\"\n- [ ] The implementation is complete.\n- [ ] Tested on target hardware (or not applicable).\n- [ ] Documentation has been added (or is not necessary).\n```\n\nAlso provide three suggestions for a PR title which completes the sentence \"If applied, this PR will...\"", "variables": [], "notes": "Summarize", "metadata": { "source": { "provider": "github-cursor-commands", "repository": "https://github.com/zauberzeug/lizard", "path": ".cursor/commands/summarize-branch.md", "ref": "cadcb9ef4e285e7434e415fd1f5e62a490c96a07", "url": "https://github.com/zauberzeug/lizard/blob/cadcb9ef4e285e7434e415fd1f5e62a490c96a07/.cursor/commands/summarize-branch.md", "key": "zauberzeug/lizard/.cursor/commands/summarize-branch.md" } } }

summarize-branch

About

Install summarize-branch and it becomes one more candidate the router can pick - when it fits.

Use it

Manifest

Reviews