Download for MacApple silicon, macOS 14+
Skill

swe-devops-standards

@muend Updated 2026-10-17

Always invoke to review, repair, or deliver geospatial or GeoAI code, including contract compliance, security, error handling, transactions, tests, scripts, functions, notebooks, packages, CI/CD, and repository changes, even when deployment is not requested. Pair with the domain skill for ETL and other production code. Covers CRS/data invariants, dependencies, cross-platform reproducibility, automation, and shipping. Do not trigger for unrelated software or analysis requesting no code or repository artifact.

agent-skillsaiai-agentsclaude-codecodexgeoaigeospatialgis

Install

With your agent

Install OMGSkills skill "muend/geoai-skills:skills/swe-devops-standards" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.

Manual command

git clone https://github.com/muend/geoai-skills /tmp/geoai-skills && ln -s /tmp/geoai-skills/skills/swe-devops-standards ~/.claude/skills/swe-devops-standards

From README

Geospatial SWE & DevOps Standards Purpose: code produced as part of geospatial work should run in the user's real environment and meet peer-level engineering quality. Apply these rules only when code or repository artifacts are in scope. Environment realities (the top error source) Script-first by default: no %matplotlib inline, !pip , or display() unless the user is explicitly in a notebook. Every file runs from a terminal via python script.py behind an if name == "main": block. (Cell markers like # %% are fine as an addition — the script must also work without them.) Cross-platform paths: always pathlib.Path; never string-concatenate or hardcode / or \\. Ask or detect the user's OS before giving shell commands; give CMD/PowerShell syntax on Windows, POSIX elsewhere — don't mix (export vs set, venv/bin/activate vs venv\Scripts\activate). Encodings: explicit encoding="utf-8" on every text file open — Windows still defaults to legacy code pages, and non-ASCII content corrupts silently.