discussion-commenter
Post Q&A entries from office hours writeups as comments to a GitHub Discussion. Use when the user wants to post writeup content to a discussion thread.
When & Why to Use This Skill
This Claude skill automates the process of publishing office hours Q&A sessions directly to GitHub Discussions. By parsing markdown writeups and leveraging the GitHub CLI, it transforms static meeting notes into interactive, searchable discussion comments, ensuring that valuable insights from live sessions are preserved and easily accessible within a project's repository.
Use Cases
- Community Engagement: Automatically sync weekly office hour summaries to a public GitHub Discussion to keep contributors and users informed.
- Documentation Workflow: Convert internal Q&A markdown files into threaded GitHub comments to facilitate team feedback and visibility.
- Knowledge Base Building: Streamline the transition from raw meeting notes to a persistent, searchable FAQ resource on GitHub for developer communities.
| name | discussion-commenter |
|---|---|
| description | Post Q&A entries from office hours writeups as comments to a GitHub Discussion. Use when the user wants to post writeup content to a discussion thread. |
Discussion Commenter
Post Q&A entries from office hours writeups as individual comments to a GitHub Discussion.
Usage
Run the script with the writeup file path, discussion URL, and date:
uv run .github/skills/discussion-commenter/post_qas.py \
"path/to/writeup.md" \
"https://github.com/orgs/ORG/discussions/NUMBER" \
"2026/01/06"
Arguments
writeup_path- Path to the markdown writeup file containing Q&Asdiscussion_url- Full URL to the GitHub discussiondate- Date string to prefix each comment (e.g., "2026/01/06")
Options
--dry-run- Parse and display what would be posted without actually posting
Requirements
- GitHub CLI (
gh) must be installed and authenticated - User must have permission to comment on the discussion
Output
Each ## Question section in the writeup becomes a separate comment, formatted as:
**2026/01/06: Question Title**
Answer content...
Subsections (### Follow-up) are included in the parent question's comment.