repo-to-content

Use when the user wants to generate a styled PDF from repository outputs using Typst with IBM Plex Sans and a clean brand palette. Triggers on phrases like "generate a PDF", "make a PDF from outputs", "typst PDF", "pdf this".

Scan a local Git repository and emit a manifest of its text sources (README, docs/, planning/, report/), embeddable images (diagrams/, graphics/, images/, banner.*), and repo metadata (name, slug, git remote, HEAD commit, derived title and summary). Shared helper invoked by the other repo-to-docs skills before they generate anything. Use when the user asks to "scan this repo for docs", "inventory the repo content", or as a first step before building a PDF, blog post, or white paper from a repository.

Synthesize a concise, first-person, technical blog post (markdown, with frontmatter) from a GitHub repository's README, docs, and planning files. Writes intro / body / conclusion in a no-marketing-fluff voice. Use when the user says "turn this repo into a blog post", "draft a blog post about this project", "write up this repo as an article", or wants a publishable narrative of the repository.

Interactive setup for the repo-to-docs plugin — writes ~/.config/repo-to-docs/config.json with author details, default license, Typst footer toggles, index-repo publishing targets, and Google Drive settings. Use when the user says "configure repo-to-docs", "set up repo-to-docs", "add a new docs-index target", "change the default license", or is running any repo-to-docs skill for the first time and hits missing config.

Publish an already-generated PDF (or other file) into a configured docs-index repository — copies it into a YY/MM/DD/<slug>/ folder, writes meta.json, runs the repo's build-index.sh if present, then commits and pushes. Use when the user says "publish this PDF to my docs index", "push this document to the public docs repo", "add this to my docs-index", or after running repo-to-pdf/white-paper and wanting to publish it.