github-ops_skill

Overview

This skill automates GitHub operations end-to-end: creating repositories, pushing code, managing releases, and updating files without user intervention. It uses a securely stored GitHub token to perform API calls and git operations. Designed for fast, reliable execution so agents can deploy code and publish releases autonomously.

How this skill works

The skill reads a securely stored GITHUB_TOKEN and calls the GitHub REST API to create repositories, create releases, and update files. For code pushes it configures a remote using the token and runs standard git add/commit/push flows in a workspace. It returns URLs and status messages for created repos, pushed branches, and releases, enabling downstream automation like continuous deployments.

When to use it

• Create a new repository programmatically without manual GitHub UI steps
• Push a local workspace or specific directory to a GitHub repo automatically
• Publish a release and tag a release version on a repository
• Update README or other tracked files via API when content changes
• Trigger an automated deployment after code push (e.g., Vercel integration)

Best practices

• Keep GITHUB_TOKEN in a secure secrets store with limited permissions (repo, workflow scopes as needed)
• Use descriptive commit messages and release notes to improve traceability
• Run operations from a controlled workspace to avoid accidental pushes from wrong branches
• Validate token permissions and repository names before performing destructive actions
• Include automated tests for create/push/release flows in CI to catch failures early

Example use cases

• Create a project repo and push initial site content, then return the repo URL to the caller
• Push a docs folder to a documentation repository and trigger the production site build
• Create a semantic-release tag and GitHub Release for a new version after tests pass
• Update README or license file across many archived repositories programmatically