com um clique
release-tweet
// Draft a release announcement tweet from a GitHub release. Use when asked to compose a tweet, draft a release announcement, or write social media copy for a new version/release.
// Draft a release announcement tweet from a GitHub release. Use when asked to compose a tweet, draft a release announcement, or write social media copy for a new version/release.
Audit and resolve GitHub pull request review comments with an evidence-based workflow. Use when asked to "address PR comments", "resolve review feedback", "handle inline comments", "reply to review threads", or "close out PR review notes".
Reconcile merge or rebase conflicts with branch-aware, regression-focused analysis. Use when asked to "resolve merge conflicts", "fix rebase conflicts", "reconcile conflicts", "rebase main", or "help me finish this merge". Detects active conflict state, guides branch selection when no operation is active, and produces a confidence-ranked reconciliation report with open questions. Treats the target branch (often `main`) as canonical for current behavior.
Produces a single-story walkthrough of AI-authored code changes from runtime trigger to final behavior, weaving changed and unchanged code into one narrative with annotated diffs, trade-offs, alternatives, and risk analysis. Use when asked to "explain what changed", "walk me through this diff", "summarize agent edits", "show how this feature works", or "explain this implementation step by step".
Update upcoming CHANGELOG release notes with user-facing outcomes. Use when asked to update changelog entries, prepare release notes, reconcile changelog content with git history, or audit release-note drafts.
Use when mining PR review feedback to extract repeatable rules/learnings, present ranked candidates, and codify approved items into AGENTS.md/CLAUDE.md with dedupe + provenance.
| name | release-tweet |
| description | Draft a release announcement tweet from a GitHub release. Use when asked to compose a tweet, draft a release announcement, or write social media copy for a new version/release. |
Compose a release announcement tweet from GitHub release notes. This skill fetches the release, summarises changes, identifies contributors, cross-references X/Twitter handles, and outputs composed text for review. It does NOT post the tweet.
Determine the repository from the current working directory or user input.
If the user specifies a tag:
gh release view <tag> --repo <owner/repo>
If no tag is given, find the latest release:
gh release list --repo <owner/repo> --limit 1
Then fetch its body:
gh release view <tag> --repo <owner/repo>
Extract the release body markdown for processing.
Parse the release markdown sections (Added, Changed, Fixed, Removed) and rewrite each item as a concise, outcome-focused bullet:
Scan release notes for attribution patterns like by [@username](https://github.com/username).
Extract GitHub usernames, then determine the repo owner:
gh api repos/<owner>/<repo> --jq '.owner.login'
Filter out:
dependabot, github-actions)The remaining usernames are external contributors.
For each external contributor, run the multi-signal verification procedure documented in references/handle-verification.md.
Classify each result as high confidence or low confidence.
Assemble the tweet using the template and rules in references/tweet-format.md.
Present two things to the user:
Example confidence table:
| GitHub | X Handle | Confidence | Reasoning |
|---|---|---|---|
| @alice | @alice_dev | High | GitHub twitter_username field set |
| @bob | bob_codes | Low | Same handle exists on X but no corroborating signals |
| @charlie | — | — | No X presence found |
The user reviews everything and posts manually.