mirror of
https://github.com/wesammustafa/opencode-primer.git
synced 2026-11-18 18:04:22 +00:00
markdownlint - Disable MD028 (no-blanks-blockquote): we intentionally separate adjacent blockquote callouts (a tip + a warning side-by-side) with a blank line; visually this renders as two callouts, which is the intent. - Switch MD029 (ol-prefix) to "one_or_ordered": both "1. / 2. / 3." and "1. / 1. / 1." (auto-renumber) are valid; the rule was hitting ordered lists that have intervening code blocks, where the lint loses count. - Add blank lines before lists in five places where MD032 fired (test.md, git-release/SKILL.md, agents.md, skills.md, migration.md). - Fix nested code-fence bug in database-engineer-prompt.md: the outer ``` was being closed by an inner ```sql; switched the outer fence to ```` (4 backticks) so the inner one stays nested. link-check - Ignore https://mcp.grep.app and https://ai.google.dev/ — the first returns 405 to HEAD requests (verified working via GET); the second trips an infinite-redirect bug in the link checker (real URL works). - Ignore github.com/anomalyco/opencode/discussions — the upstream repo currently has discussions disabled. - Add 405 to aliveStatusCodes for endpoints that accept GET but reject HEAD.
1.6 KiB
1.6 KiB
name, description, license, compatibility, metadata
| name | description | license | compatibility | metadata | ||||
|---|---|---|---|---|---|---|---|---|
| git-release | Draft release notes from merged PRs, propose a semver bump, and emit a copy-pasteable `gh release create` command. Use when preparing a tagged GitHub release. | MIT | opencode |
|
What I do
- Read recent merged PRs since the last tag and group them:
- Features (
feat:commits) - Fixes (
fix:) - Other (
refactor:,perf:,docs:,chore:, …)
- Features (
- Propose a semver bump based on the diff:
- Major if any breaking changes (look for
BREAKING CHANGE:footers or!:markers) - Minor if any features
- Patch otherwise
- Major if any breaking changes (look for
- Emit a clean release-notes draft in Keep-a-Changelog format.
- Print a ready-to-run command:
gh release create v<version> --title "<title>" --notes-file release-notes.md
When to use me
When the user is preparing a tagged release. Triggers include:
- "draft release notes"
- "prepare a release"
- "what's in v1.X.Y?"
Ask the user to confirm the proposed version bump before running anything destructive (tag creation, release publish).
What I need from the repo
ghCLI must be authenticated.- The repo should have at least one prior tag — if not, propose
v0.1.0. - Conventional-commit messages are ideal but not required; without them, I'll group by PR labels or fall back to plain summaries.
What I won't do
- Push tags or publish releases without explicit confirmation.
- Edit the working tree.
- Generate fictional changelog entries — if a PR is unclear, I quote the original PR title verbatim and flag it for review.