Skip to content
Back to skills

Poly And Release Workflow

ASecurity

Commit step lint/test/harness order

  • 105 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added September 3, 2026
ai-agentstypescriptrustgobashreactexpressdjango

Works with

  • cli

Security analysis

A100/100

Scanned September 3, 2026

npx -y skills add Goldziher/basemind --skill poly-and-release-workflow --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Poly And Release Workflow?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Poly And Release Workflow
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/goldziher-poly-and-release-workflow/badge)](https://www.skillsdirectory.com/skills/goldziher-poly-and-release-workflow)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
priority: medium
description: "Commit step lint/test/harness order"
---

# Poly + Release Workflow

The canonical order to run before pushing a change. Each step gates the next; do not skip.

## Local check loop

```bash
cargo fmt
cargo clippy --workspace --all-targets --tests -- -D warnings
cargo test --workspace
poly lint .
```

Why this order:

- `cargo fmt` first so clippy / poly don't fail on formatting.
- Clippy strict (`-D warnings`) — surface real issues before the broader poly sweep.
- Unit + integration tests catch logic regressions before the slow harness.
- `poly lint .` is the meta-linter: typos, markdownlint (120-char cap), cargo-deny licenses, cargo-machete unused deps, rustdoc-lint, rust-max-lines (1000-line cap on `src/**/*.rs`).

## Harden harness

After the local loop passes:

```bash
BASEMIND_HARDEN_NO_BUILD=1 \
  cargo test --release --test harden -- --ignored --nocapture \
  2>&1 | tee /tmp/basemind-harden-$(date +%s).log
```

- `BASEMIND_HARDEN_NO_BUILD=1` reuses `target/release/basemind` — saves ~30s per run. Drop it when you're suspicious the binary is stale.
- Expect 8/8 green: ripgrep, tokio, typescript, react, django, requests, gin, ripgrep-shallow.
- Canaries: tokio `spawn_hits >= 200`, django `get_hits >= 200`, react `useState_hits >= 20`, ripgrep-shallow `any_truncated == true`.

## Commit + push

- Conventional Commit prefix (`feat:`, `fix:`, `perf:`, `chore:`, `refactor:`).
- Body explains *why*. Mention schema bumps (`INDEX_SCHEMA_VER` / blob format) and added dependencies.
- Co-author trailer per repo convention.
- Push directly to `main` is approved for the active iteration loop; PRs only when explicitly requested.

## When something fails

- typos: fix the misspelling; prefer the dictionary correction unless it's a proper noun.
- markdownlint MD013 (line length > 120): split the line; for table cells, shorten the cell or move details to a code block under the table.
- cargo-deny license rejection: add the SPDX expression to `deny.toml`'s `licenses.allow` only if the license is genuinely permissive (Apache, MIT family, ISC, 0BSD, BSL, Unicode). Anything copyleft (GPL family) — escalate.
- rust-max-lines: extract a submodule or helper file. Do not raise the cap.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.