agentleFS
acailicacailic/agent_debugger/.claude/skills/release-check/SKILL.md

release-check

Skill9 starsChanged 7 months agoMITView on GitHub

Run full validation suite before release. Sequential lint, security scan, tests, and frontend build with fail-fast behavior.

  • Installs packages

14 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use review.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • SentrySkill

    review

    Fixture review skill.

    Also in 5 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 12 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run pre-release validation checks in sequence.

    line 8
  2. Very specific:

    Verify working directory contains pyproject.toml (repo root)

    line 19
  3. Distinctive:

    Run each check in order, timing execution

    line 20
  4. Distinctive:

    If error output ≤ 50 lines: show full output

    line 38
  5. Very specific:

    If error output > 50 lines: show first 20 lines, ...

    line 39
  6. Distinctive:

    If a tool is not installed, show:

    line 43

“Common” is measured: kept by at least 6 in 10 of the 12 edited versions of this file we could read. “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

Release Check

Run pre-release validation checks in sequence.

Checks

  1. Lint: ruff check . (timeout: 60s)
  2. Security: bandit -r -ll agent_debugger_sdk api collector storage auth redaction (timeout: 120s)
  3. Tests: pytest -q (timeout: 300s)
  4. Frontend: cd frontend && npm run build (timeout: 180s)

Process

  1. Verify working directory contains pyproject.toml (repo root)
  2. Run each check in order, timing execution
  3. On failure:
    • Show error output (truncate >50 lines: first 20, last 20, with count)
    • Show remediation suggestion (see below)
    • Stop immediately
  4. On all success: Print summary with timings

Failure Remediation

CheckSuggestion
Lint"Fix lint errors above. Run ruff check . --fix for auto-fixable issues."
Security"Review security findings above. Add # nosec comments only if justified."
Tests"Fix failing tests. Run pytest -v for verbose output."
Frontend"Fix TypeScript/build errors above. Check frontend/src/ for issues."

Error Output Truncation

  • If error output ≤ 50 lines: show full output
  • If error output > 50 lines: show first 20 lines, ... N lines omitted ..., last 20 lines

Missing Dependencies

If a tool is not installed, show:

  • bandit: ⚠ bandit not found. Install with: pip install bandit
  • npm: ⚠ npm not found. Ensure Node.js is installed.

Output Format

🔍 Running release check...

1/4 Lint (ruff)............ ✓ (0.5s)
2/4 Security (bandit)...... ✓ (1.2s)
3/4 Tests (pytest)........ ✓ (12.3s)
4/4 Frontend build........ ✓ (3.1s)

✓ Release check passed. Ready to ship.

Example Failure Output

🔍 Running release check...

1/4 Lint (ruff)............ ✓ (0.5s)
2/4 Security (bandit)...... ✗ (1.2s)

Finding: [MEDIUM] Use of assert detected (security issue)
Location: tests/test_example.py:42

... 15 lines omitted ...

Review security findings above. Add `# nosec` comments only if justified.

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.