Sno Station
Sno Station is your agents' workstation: open-source software that turns the AI agents you already run into one squad on your own machine. Two heads are better than one, and they get better with every
Bucket for OpenShift Edge Team tooling that supports team operations and developer workflow.
PluginsPython · ShellGitHub @openshift-engSelf-installOwner unconfirmed
Paste into Claude or ChatGPT for installation instructions suited to your environment.
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Installable projects can be verified without a deployment domain. Use GitHub sign-in for a personal repository, or the repository verification file above for an organization repository.
Ask about other verification options
Loading the full README. The saved excerpt is shown below.
Automation, AI skills, and deployment tools for OpenShift edge engineering. This repo is the OpenShift Edge team's shared toolkit — it provides cluster deployment automation for edge topologies (two-node HA, SNO, LVM), CI and release workflow tooling, and a Claude Code plugin marketplace that gives engineers AI-assisted skills for day-to-day work.
make setup-githooks installs a pre-commit hook that runs markdownlint on staged .md files.
Prerequisites: Node.js (for markdownlint), Python 3, Bash.
Each deployment tool has its own prerequisites — see the component README for what you need.Read the full README ↗Automation, AI skills, and deployment tools for OpenShift edge engineering. This repo is the OpenShift Edge team's shared toolkit — it provides cluster deployment automation for edge topologies (two-node HA, SNO, LVM), CI and release workflow tooling, and a Claude Code plugin marketplace that gives engineers AI-assisted skills for day-to-day work.
| Use case | Component |
|---|---|
| Two-node HA cluster (arbiter or fencing) | two-node-toolbox/ |
| EC2 dev host or hypervisor | ec2-deploy/ |
| Automatic EC2 shutdown and weekly Slack report | watchman/ |
| Single Node OpenShift with DU config | sno-deploy/ |
| LVM Operator development workspace | environments/lvm-operator/ |
| Nightly payload health monitoring | payload-monitor/ |
| Component Readiness triage report (HA vs edge) | ci-tooling/readiness-report/ |
| Multi-repo workspace management | workspace plugin via the marketplace |
| Claude Code plugins for edge workflows | plugins/ via the marketplace |
git clone [email protected]:openshift-eng/edge-tooling.git
cd edge-tooling
make setup-githooks
make setup-githooks installs a pre-commit hook that runs markdownlint on staged .md files.
Prerequisites: Node.js (for markdownlint), Python 3, Bash.
Each deployment tool has its own prerequisites — see the component README for what you need.
From within Claude Code:
/plugin marketplace add openshift-eng/edge-tooling
Then enable whichever plugins you need. See the plugin README for details.
| Plugin | What it does |
|---|---|
| challenge | Adversarial hypothesis reviewer for root cause analysis |
| edge-ic | IC workflow automation — TODOs, status reports, Jira updates |
| edge-ocp-ci | Monitor nightly payload health across edge topologies with AI-enriched analysis |
| edge-ocp-rc | RC testing for OCP edge topologies (TNF, TNA, SNO) — launch Prow jobs, track results, classify failures |
| edge-scrum | Scrum process management — refinement, sprint planning, standups |
| github | GitHub workflow skills — PR automation, labeling, queue management |
| lvms | LVMS release, QE, and operational workflows |
| lvms-ci | LVMS CI automation — failure triage, Prow job analysis |
| mcp-atlassian | Atlassian Jira MCP server for Claude Code |
| microshift-ci | MicroShift CI failure analysis and JIRA bug creation |
| Directory | What it does |
|---|---|
| two-node-toolbox/ | Deploy two-node OpenShift clusters (arbiter/fencing topologies) |
| ec2-deploy/ | Spin up EC2 instances for development and hypervisor use |
| watchman/ | Stop stale EC2 instances and send weekly Slack reports |
| sno-deploy/ | Deploy Single Node OpenShift with DU configuration |
| payload-monitor/ | Nightly payload health monitoring for edge topologies |
| environments/lvm-operator/ | Development workspace for the LVM Storage operator |
| Directory | What it does |
|---|---|
| ci-tooling/ | Collection of standalone CI helpers |
| ci-tooling/readiness-report/ | Sippy Component Readiness report for HA vs TNF/TNA/SNO |
| Resource | What it covers |
|---|---|
| AGENTS.md | Repo overview, tool routing, component-level guides |
| CONTRIBUTING.md | Contribution model, code standards, architectural patterns |
| docs/claude/workflows.md | Deployment walkthroughs and Component Readiness reports |
| docs/claude/prerequisites.md | Required credentials and tools |
| Component READMEs | Per-tool setup, prerequisites, and usage |
PRs use the fork model — push to your fork, open a PR against main. See CONTRIBUTING.md for details.
| microshift-dev | MicroShift dev tools collection |
| microshift-release | MicroShift release testing automation |
| pr-review | PR lifecycle toolkit — vet findings, triage CodeRabbit reviews, yolo-agent |
| skills-review | Lint SKILL.md files for quality and correctness |
| threat-model | Security threat analysis for OpenShift PRs |
| two-node | Two-node topology workflow automation — RHEL verification, Jira integration |
| workspace | Multi-repo workspace manager for cross-project AI-assisted development |