sync-github-repo-metadata
Inspect a repository and propose or apply GitHub About metadata updates. Use when Codex needs to infer a concise repository description and topic set from source code, package metadata, docs config, or the current README, then preview and optionally run `gh repo edit`.
Works with
--- name: sync-github-repo-metadata description: Inspect a repository and propose or apply GitHub About metadata updates. Use when Codex needs to infer a concise repository description and topic set from source code, package metadata, docs config, or the current README, then preview and optionally run `gh repo edit`. license: MIT --- # Sync GitHub Repo Metadata Use the repository and its configuration as the source of truth. Treat the current README, docs, and existing GitHub metadata as weak hints unless they still match the codebase. ## Workflow 1. Gather repo facts. 2. Read the current remote metadata with: - `gh repo view --json nameWithOwner,description,repositoryTopics,homepageUrl,url` 3. Infer: - one concise repository description - a focused topic set based on actual language, framework, domain, and tooling 4. Preview the current values, proposed values, and the exact `gh repo edit` command. 5. Apply changes only after explicit confirmation. ## Guidelines - Do not change homepage or other repo settings unless the user explicitly asks. - Focus on GitHub description and topics only. - Prefer a single-sentence description that matches the repo's real purpose. - Prefer accurate, specific, stable topics over broad buzzwords. - Prefixing description with an emoji is encouraged. - Remove stale topics instead of only appending new ones. - Use lowercase kebab-case topics. ## Preview Format - Current description - Proposed description - Current topics - Proposed topics - Exact `gh repo edit` command with `--description`, `--add-topic`, and `--remove-topic` arguments as needed ## Apply Step - Never apply blindly. - After confirmation, run the exact previewed command. - If authentication or permissions fail, report the command and the failure instead of guessing an alternative.
More Writing & Documentation skills
paper-context-resolver
lllllllama/rigorpilot-skills
Rigor Paper Context helper for README-first deep learning repo reproduction. Use only when the README and repository files leave a narrow reproduction-critical gap and the task is to resolve a specific paper detail such as dataset split, preprocessing, evaluation protocol, checkpoint mapping, or runtime assumption from primary paper sources while recording conflicts. Do not use for general paper summary, repo scanning, environment setup, command execution, title-only paper lookup, or replacing README guidance by default.
repo-intake-and-plan
lllllllama/rigorpilot-skills
Rigor Intake helper for README-first deep learning repo reproduction. Use when the task is specifically to scan a repository, read the README and common project files, extract documented commands, classify inference, evaluation, and training candidates, and return the smallest trustworthy reproduction plan to the main orchestrator. Do not use for environment setup, asset download, command execution, final reporting, paper lookup, or end-to-end orchestration.
minimal-run-and-audit
lllllllama/rigorpilot-skills
Rigor Run skill for README-first deep learning repo reproduction. Use when the task is specifically to capture or normalize evidence from the selected smoke test or documented inference or evaluation command and write standardized `repro_outputs/` files, including patch notes when repository files changed. Do not use for training execution, initial repo intake, generic environment setup, paper lookup, target selection, hidden scientific-meaning changes, or end-to-end orchestration by itself.
