// Use when pulling live GitHub state back into existing gh-infra manifests with `gh infra import --into`, especially for write/patch/skip decisions, shared file sources, template-backed files, and import safety rules.
Complete YAML schema reference for File and FileSet resources. Use when writing manifests to manage files (CODEOWNERS, LICENSE, CI workflows, etc.) in one or more repositories, including templating, patches, reconcile modes, delivery method, and import-into behavior.
Complete YAML schema reference for Repository and RepositorySet resources. Use when writing or editing manifests for repo settings, labels, actions, branch protection, rulesets, secrets, variables, or repository defaults.
CI/CD integration patterns for gh-infra: auto-apply on merge, scheduled drift detection, self-managed vs central-management layouts, and authentication setup for GitHub Actions workflows.
Overview of gh-infra and command workflow (import, validate, plan, apply). Use when managing GitHub repository settings, labels, actions settings, rulesets, secrets, variables, or files declaratively via YAML manifests.
Use when running demo recordings, diagnosing recording failures, or regenerating GIFs from existing MP4s. Covers the Docker + VHS + ffmpeg pipeline.
Use when creating new VHS demo tapes or editing existing ones. Covers tape syntax, setup scripts, mock-gh data layout, and the checklist for adding a new demo end-to-end.
| name | import-into |
| description | Use when pulling live GitHub state back into existing gh-infra manifests with `gh infra import --into`, especially for write/patch/skip decisions, shared file sources, template-backed files, and import safety rules. |
Use this skill for gh infra import --into=....
This workflow is different from normal import, plan, and apply:
Use this skill when the user wants to:
write, patch, and skipgh infra import <owner/repo> [owner/repo ...] --into=<path>
<path> may be a file or a directory of manifests.
Repository, RepositorySet, and FileSetwrite: update the normal local targetpatch: store the drift under patches:skip: ignore for this runTypical defaults:
writewritepatchpatches: entry: patchcreate_only entries: skipThere are two skip modes:
Hard-skip cases include:
github:// sourcesFor templates such as <% .Repo.Name %> and <% .Repo.FullName %>, gh-infra compares:
It then tries to reconstruct updated local template source while preserving placeholders.
Use write only when you want to update the underlying shared source. Use patch when drift should stay repository-specific.
source: ./... files: written back to the source filegithub:// sources: no local write target