agentsclimarketplace
Sign in

Python ci

Skill nyquistwilder/personal-pi/skills/python-ci

Python continuous integration workflow for reproducible uv installs, lockfile-aware jobs, lint/type/test/coverage stages, matrix testing, caching, artifacts, security checks, and release gates aligned with local wrappers.From its SKILL.md

Install
npx -y skills add nyquistwilder/personal-pi --skill python-ci

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.3 KB, 442 tokens by cl100k_base, as published. Nobody here has run it

Python CI

Rule

Keep CI aligned with local validation. CI should run the same repository wrapper commands that developers run, with reproducible uv installs and lockfile-aware behavior.

Use this skill for CI configuration or review. Use python-release for publishing workflows and release automation.

Hard Stops

Stop and ask before changing CI when:

  • The CI provider, branch protections, required checks, or secret availability is unclear.
  • Changes may publish packages, create tags/releases, deploy, rotate secrets, or mutate remote systems.
  • The repository is a monorepo and project selection/matrix policy is unspecified.
  • Caches, artifacts, or logs may expose secrets or sensitive data.
  • Adding new tools would diverge from local just check or mise run check without approval.

CI Defaults

  • Install and use uv reproducibly.
  • Respect uv.lock with frozen or locked installs where appropriate.
  • Run local wrappers such as just check; do not duplicate long command lists unless needed.
  • Separate lint, type, test, build, and release gates when useful, but keep local parity.
  • Cache uv and Python dependencies safely using lockfile keys.
  • Upload coverage or build artifacts only when explicitly needed.
  • Keep generated artifacts out of git.

Workflow

  1. Inspect local task wrappers, pyproject.toml, lockfiles, Nix/mise setup, and existing CI.
  2. Identify required checks and project matrix.
  3. Add or modify jobs to install tooling and run wrapper commands.
  4. Ensure CI does not rely on undeclared machine state or unpinned external behavior.
  5. Validate YAML syntax where possible.
  6. Run local just check and any CI-equivalent command available locally.

Review Guidance

Flag CI that bypasses local wrappers, ignores lockfiles, runs tests without coverage policy, uses broad secrets, has unsafe pull-request secret exposure, uploads unnecessary artifacts, or performs irreversible release/deploy actions without gates.

Completion

Report CI files changed, jobs/checks added, local parity commands, cache/artifact behavior, secrets or permission considerations, and validations run.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 326,736. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.