How do I install the Github Ops skill?

Run npx skillmds@latest add automateyournetwork/github-ops in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Github Ops safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Github Ops?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Github Ops free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under Apache-2.

Who published Github Ops?

automateyournetwork (@automateyournetwork) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Github Ops by automateyournetwork — Agent Skill

Name: Github Ops
Author: automateyournetwork

Github Ops

GitHub repository operations — issues, PRs, code search, and config-as-code workflows. Use when creating a GitHub issue for a network finding, opening a pull request for a config change, searching repos for IP or VLAN references, or committing an audit report to a repository.

File contents

GitHub Operations Skill

Available Capabilities

Repository Operations

Search repositories, list branches, get file contents
Create/update files, create branches
Compare branches, list commits

Issues

Create, list, search, update, and comment on issues
Use issues to track network findings, audit results, and remediation tasks

Pull Requests

Create PRs for config changes, list PRs, get PR details
Review and merge PRs, add comments

Code Search

Search across repositories for configuration patterns
Find references to specific IPs, VLANs, ACLs in config repos

GitHub Actions

List workflow runs, get workflow status
Trigger workflows for automated testing

Workflow Patterns

Network Finding → GitHub Issue

When you discover a network problem (via pyATS, health check, etc.):

Create a GitHub issue with the finding details
Include device name, symptom, recommended fix
Label appropriately (bug, security, performance)
Reference the GAIT session ID for audit trail

Config Change → Pull Request

When a config change is approved:

Create a branch from main
Commit the new/updated config file
Open a PR with change details and ServiceNow CR number
Link the PR in the GAIT audit trail

Audit Report → Repository

After health checks or audits:

Commit the report as a markdown file
Organize by date: reports/YYYY-MM-DD/
Include raw data and AI analysis

Environment Variables

GITHUB_PERSONAL_ACCESS_TOKEN — GitHub PAT with repo access

Important Rules

Never commit secrets, passwords, or API keys to repositories
Always create a branch for changes — never push directly to main
Include meaningful commit messages describing the network change
Reference ServiceNow CR numbers in PR descriptions when applicable

---name: github-opsdescription: GitHub repository operations — issues, PRs, code search, and config-as-code workflows. Use when creating a GitHub issue for a network finding, opening a pull request for a config change, searching repos for IP or VLAN references, or committing an audit report to a repository.license: Apache-2.0---# GitHub Operations Skill## Available Capabilities### Repository Operations- Search repositories, list branches, get file contents- Create/update files, create branches- Compare branches, list commits### Issues- Create, list, search, update, and comment on issues- Use issues to track network findings, audit results, and remediation tasks### Pull Requests- Create PRs for config changes, list PRs, get PR details- Review and merge PRs, add comments### Code Search- Search across repositories for configuration patterns- Find references to specific IPs, VLANs, ACLs in config repos### GitHub Actions- List workflow runs, get workflow status- Trigger workflows for automated testing## Workflow Patterns### Network Finding → GitHub IssueWhen you discover a network problem (via pyATS, health check, etc.):1. Create a GitHub issue with the finding details2. Include device name, symptom, recommended fix3. Label appropriately (bug, security, performance)4. Reference the GAIT session ID for audit trail### Config Change → Pull RequestWhen a config change is approved:1. Create a branch from main2. Commit the new/updated config file3. Open a PR with change details and ServiceNow CR number4. Link the PR in the GAIT audit trail### Audit Report → RepositoryAfter health checks or audits:1. Commit the report as a markdown file2. Organize by date: `reports/YYYY-MM-DD/`3. Include raw data and AI analysis## Environment Variables- `GITHUB_PERSONAL_ACCESS_TOKEN` — GitHub PAT with repo access## Important Rules- Never commit secrets, passwords, or API keys to repositories- Always create a branch for changes — never push directly to main- Include meaningful commit messages describing the network change- Reference ServiceNow CR numbers in PR descriptions when applicable

Frequently asked questions