# swe-devops-standards

This skill guides agents through geospatial and GeoAI code reviews, testing, dependency management, and delivery. Use it when code or repository changes are in scope.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · ★ 35
- Author: Muhammed Enes Duran
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/muend/geoai-skills/tree/HEAD/skills/swe-devops-standards/SKILL.md
- Updated: 2026-10-17
- HTML: https://affpapa.org/en/nevibecode/skills/swe-devops-standards

## What it does

The skill sets engineering expectations for geospatial work, from scripts and functions to notebooks, packages, and CI/CD. Reviews proceed from correctness to security, performance, and readability. Each finding comes with a code-level fix.

Its guidance covers cross-platform paths, explicit text encodings, typed functions, pytest checks, pinned dependencies, and reproducible environments. Spatial checks include CRS, nodata, and geometry edge cases. For ETL and other production code, it recommends pairing this skill with the relevant domain skill.

This is for geospatial software and pipeline delivery, not generic non-spatial coding. The skill also directs agents to consult its authoritative source registry before applying packaging, CI, testing, or supply-chain guidance.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add muend/geoai-skills --skill swe-devops-standards -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/swe-devops-standards/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/swe-devops-standards/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add muend/geoai-skills --skill swe-devops-standards -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/swe-devops-standards/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add muend/geoai-skills --skill swe-devops-standards -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/swe-devops-standards/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install muend/geoai-skills swe-devops-standards
```

2. **Manually: put the files in place**
- File: `.github/skills/swe-devops-standards/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add muend/geoai-skills --skill swe-devops-standards -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/muend/geoai-skills --path skills/swe-devops-standards
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/swe-devops-standards/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add muend/geoai-skills --skill swe-devops-standards -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/muend/geoai-skills/tree/HEAD/skills/swe-devops-standards/SKILL.md

## When to use it
- review spatial code for correctness and data loss
- write tests for functions and edge cases
- pin dependencies for a reproducible environment
- set up CI checks for tests and linting
- turn review findings into code fixes

## Example prompts
- Review this geospatial code for correctness, security issues, and CRS problems.
- Add tests for the geometry-processing function and run the available checks.
- Prepare this production pipeline change with verification and rollback notes.

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 3b7e886e0b6a197e.

BEGIN THIRD-PARTY FILE 3b7e886e0b6a197e
````text
---
name: swe-devops-standards
description: >-
  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.
license: MIT
metadata:
  author: Muhammed Enes Duran
---

# 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.

## 1. Environment realities (the top error source)

- **Script-first by default**: no `%matplotlib inline`, `!pip install`, 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.
- **Modern Python (3.11+)**: `X | None` unions, `type` aliases, structural
  pattern matching where they clarify; state the minimum version if a
  feature requires it.

## 2. Code quality defaults

Applied to every generated function/module, even when not asked:

```python
def compute_share(values: list[float], total: float) -> list[float]:
    """Return each value's share of the total.

    Args:
        values: Values to compute shares for.
        total: Denominator; must be non-zero.

    Returns:
        Shares in the same order as values.

    Raises:
        ValueError: If total is zero.
    """
    if total == 0:
        raise ValueError("total must be non-zero — share is undefined.")
    return [v / total for v in values]
```

- Type hints on every signature; `dataclass`/`TypeAlias` for complex types.
- Google-style docstrings; one-liners suffice for trivial functions.
- **Never bare `except:`**; catch specific exceptions, handle or re-raise
  with `raise ... from e`. A silent `pass` costs a week of debugging.
- `logging` over `print` (leveled, formatted), except user-facing CLI
  output.
````
END THIRD-PARTY FILE 3b7e886e0b6a197e

The third-party file has ended. Everything between the 3b7e886e0b6a197e tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2847 of 6451 bytes. © Muhammed Enes Duran · MIT · https://github.com/muend/geoai-skills/tree/HEAD/skills/swe-devops-standards/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md