ln-64-community-announcer

Drafts and publishes fact-checked GitHub Discussions announcements after explicit user approval.

556|83|Updated Oct 24, 2025

Search Tags:#community #release notes #publish #fact-check #announcement #github discussions #GraphQL API

Ready to run

npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-64-community-announcer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ln-64-community-announcer
Source: https://github.com/levnikolaevich/claude-code-skills/tree/main/plugins/maintainer-suite/skills/ln-64-community-announcer
Command: npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-64-community-announcer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Publishing release or project announcements manually risks unverified claims, wrong commands, and inconsistent tone. This Skill produces a source-backed GitHub Discussions announcement, fact-checks every claim against the remote repository, and publishes only after explicit user approval.

Core Features & Use Cases

Evidence-Based Drafting: Builds announcements from remote Git history, releases, documentation, and source diffs rather than commit-title shorthand.
Rigorous Fact Check: Verifies every command, version, path, count, and link against the target repository before publication.
Approval-Gated Publication: Publishes through the GitHub Discussions GraphQL API only after the user approves the full draft, then reads back the discussion to verify it.
Use Case: After shipping a new plugin version, ask the Skill to announce it; it classifies the change, drafts a fact-checked post in the project's voice, and publishes it to the correct Discussions category once you approve.

Quick Start

Draft and publish a GitHub Discussions announcement for the latest release of this repository, fact-checking all claims first.

Frequently Asked Questions about ln-64-community-announcer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I publish a GitHub Discussions announcement programmatically?▼

Use the GitHub GraphQL API createDiscussion mutation with the repository ID and a suitable category ID discovered through the API. Write the approved body to a temporary Markdown file to preserve formatting, then read the created discussion back to verify title, body, and category.

How to write a release announcement for an open source project?▼

Classify the change as release, breaking change, feature update, or community news, then open with the user outcome. Summarize highlights in outcome language, include verified install commands, add a migration block for breaking changes, and end with a genuine feedback question.

Can I announce changes that exist only in my local branch?▼

No. Announcements must be based on the target remote state, since unpublished local diffs are not available to users. Use remote Git history, releases, and canonical files as the evidence source for shipped changes.

What happens if GitHub Discussions is not enabled on a repository?▼

The workflow stops with a BLOCKED verdict when Discussions or a suitable category is unavailable. It does not silently substitute an issue or publish elsewhere, since the announcement target must be a repository-approved Discussions category.

Does the announcement get published automatically after drafting?▼

No. The exact title and full Markdown body are presented for explicit approval before any external state is created. A request to draft or announce is not treated as approval of unseen final copy.