agentleFS
kunalsurikunalsuri/1000x-Agent-Skills/.agents/skills/cross-platform-dev-scripts/SKILL.md

cross-platform-dev-scripts

Skill2 starsChanged 17 days agoApache-2.0View on GitHub

Generates and validates turnkey, cross-platform dev setup and test scripts (scripts/win and scripts/linux) with dual-engine uv/venv support. Use when setting up a repository for local onboarding, adding Windows and Linux dev scripts, or verifying script parity.

  • Deletes or force-pushes

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 2 are distinctive, and 6 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never mandates external downloads or pipes unverified scripts into a shell.

    line 30
  2. Very specific:

    Never requires sudo or Administrator escalation.

    line 34
  3. Very specific:

    All paths and cleanup routines (rm -rf -- "$VENV_DIR") are strictly quoted.

    line 35
  4. Very specific:

    Test filtering: supports -k <expr> (Bash) and -K <expr> (PowerShell) for fast local iteration.

    line 40
  5. Very specific:

    If the project requires multiple requirements files (e.g.

    line 64
  6. Very specific:

    If tests require specific local environment flags (e.g.

    line 66
  7. Very specific:

    If the project has linting or type-checking steps (e.g.

    line 68
  8. Distinctive:

    Run the verification tool to audit the created scripts for safety invariants and cross-platform parity:

    line 73

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Cross-Platform Dev Scripts & Local Onboarding

Purpose

Provides a standardized, atomic workflow to equip any repository with hardened, turnkey developer setup and test scripts:

  • scripts/linux/dev-setup.sh (Linux / macOS / WSL)
  • scripts/linux/dev-test.sh
  • scripts/win/dev-setup.ps1 (Windows PowerShell 5.1 / 7+)
  • scripts/win/dev-test.ps1

Empowers any contributor or autonomous agent to clone a repository and immediately run setup and test commands with zero configuration friction.


Architectural Principles

  1. Dual-Engine Acceleration (uv + venv):
    • Uses uv when installed on the user's PATH for 10x–100x faster package resolution.
    • Automatically and gracefully falls back to the Python standard library's venv + pip when uv is absent.
    • Never mandates external downloads or pipes unverified scripts into a shell.
  2. Strict Hermetic Isolation (Least Privilege):
    • Everything is confined strictly to .venv/ at the repository root.
    • Never requires sudo or Administrator escalation.
    • All paths and cleanup routines (rm -rf -- "$VENV_DIR") are strictly quoted.
  3. Parity & Developer Experience (DX):
    • Identical test targets and step sequences between Windows PowerShell and Linux Bash.
    • Auto-bootstrap: dev-test runs dev-setup automatically if the virtual environment does not exist yet.
    • Test filtering: supports -k <expr> (Bash) and -K <expr> (PowerShell) for fast local iteration.

Procedural Workflow

Phase 1: Heavy-Lifting Scaffolding

Inspect the target project root and execute the built-in generator script:

python <skill_path>/scripts/scaffold_dev_scripts.py --target . [--requirements requirements-dev.txt] [--test-cmd "-m pytest"]

The script automatically:

  1. Detects project manifests (requirements-dev.txt, requirements.txt, pyproject.toml, etc.).
  2. Creates scripts/linux/ and scripts/win/ directories idempotently.
  3. Generates the 4 hardened scripts with proper permissions (0o755 for .sh scripts).
  4. Outputs a JSON summary of generated files.

Phase 2: Semantic Tailoring (Agent Review)

Inspect the generated scripts and tailor them to any project-specific constraints:

  1. Requirements & Build Tools:
    • If the project requires multiple requirements files (e.g. requirements.txt + requirements-dev.txt), update the setup scripts to install both.
  2. Environment Variables & Secrets:
    • If tests require specific local environment flags (e.g. TESTING=1 or PYTHONPATH=.), configure them in dev-test.sh and dev-test.ps1.
  3. Multi-Step Test Pipelines:
    • If the project has linting or type-checking steps (e.g. ruff check, mypy), add corresponding run_step (Bash) and Invoke-Step (PowerShell) invocations in both test scripts in identical order.

Phase 3: Parity & Safety Verification

Run the verification tool to audit the created scripts for safety invariants and cross-platform parity:

python <skill_path>/scripts/validate_dev_scripts.py --target .

The validator verifies:

  • Script presence and shebang formatting.
  • Strict error handling (set -Eeuo pipefail in Bash, $ErrorActionPreference = "Stop" in PowerShell).
  • Safe quoting and isolation (no sudo invocations, no piping remote scripts to a shell, no writes outside .venv/).
  • Cross-platform step parity and filter support.
  • Static syntax checking (bash -n and PowerShell AST parsing when tooling is present).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.