ghchinoy/repo-authoring
Repository management skills for technical writing, editorial report artifacts, README generation, changelog curation, and commit recaps.
Generates, updates, and curates a CHANGELOG.md file adhering to the Keep a Changelog v1.1.0 specification and Common Changelog style guide by analyzing bd issue tracking history and git commit history.
Author standalone, zero-dependency HTML technical experiment records, benchmark ablations, and architecture briefings using a warm editorial design system, offline semantic HTML mathematical typography, inline SVG schematics, interactive pipeline explorers, and claim-to-code verification matrices. Use when asked to create a rich HTML report, experiment ledger artifact, or interactive technical briefing.
Execute upstream issue creation, git fork synchronization (upstream vs origin), and pull request submission in headless or sandbox environments where SSH keys require passphrases or GitHub OAuth tokens lack workflow scope.
Create, assess, and improve README.md files for public GitHub projects. Scores an existing README against a weighted rubric, gives targeted section-by-section fixes, and can check strict standard-readme spec compliance. Use when the user asks to write a README, review/grade a README, improve an existing README, or check standard-readme compliance.
Generates a structured weekly or custom timeframe commit recap for a repository. Looks for repository-specific categorization rules in .gemini/recap-rules.md or GEMINI.md before fetching git logs via git log --stat to accurately organize changes (e.g. core vs experiments). Supports optional audio generation.
Edit and review technical blog posts, specs, and engineering write-ups to ensure clean house-style conformity and pitch-appropriate readability. Use as a post-hoc acceptance gate or review tool.