als-apg/osprey-pre-commit
src/osprey/assist/integrations/claude_code/pre-commit/SKILL.md
Validates code before committing. Runs linting, formatting, and tests to catch issues early. Use when ready to commit, before pushing, or when the user asks to run checks, validate, or verify their changes.
$ install --global
skillsauthnpx skillsauth add als-apg/osprey osprey-pre-commitInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 3, 2026, 4:00 PM4.1s1 file scanned
SKILL.md
- name:
- osprey-pre-commit
- description:
- >
- allowed-tools:
- Read, Glob, Grep, Bash, Edit
Pre-Commit Validation
This skill helps you validate your code changes before committing.
Instructions
Follow the validation workflow in instructions.md.
Quick Command Reference
Quick Check (Before Commits)
# Auto-fix code style
ruff check src/ tests/ --fix --quiet || true
ruff format src/ tests/ --quiet
# Run fast tests
pytest tests/ --ignore=tests/e2e -x --tb=line -q
Or use the script:
./scripts/quick_check.sh
Full CI Check (Before Pushing)
./scripts/ci_check.sh
Workflow
- Auto-fix formatting and simple lint issues
- Run tests to catch regressions
- Fix failures if any tests fail
- Re-run until all checks pass
- Commit with confidence
When to Use Each Check
| Situation | Command |
|-----------|---------|
| Ready to commit | ./scripts/quick_check.sh |
| Ready to push | ./scripts/ci_check.sh |
| Creating PR | ./scripts/premerge_check.sh main |
Related Skills
als-apg/osprey-build-interview
development
VerifiedTrustedCommunity
Interactive interview to create a custom OSPREY build profile for a new accelerator, detector, or beamline application. Use when someone says "interview me", "create a build profile", "set up my agent", "configure my detector", "onboard me", or needs to create an OSPREY project tailored to their specific control system. Also handles migration from existing OSPREY projects (including LangGraph-era projects) — trigger on "migrate my project", "I have an existing project", "upgrade from old OSPREY", "upgrade from langgraph", "legacy migration", "bring my project forward", "convert my project", "extract profile from existing project", "reverse-engineer build profile". Also use for /osprey-build-interview feedback to collect post-use feedback. Also trigger when onboarding a new colleague or when anyone needs help figuring out what their OSPREY agent should look like.
59SKILL.mdUpdated May 6, 2026
als-apg/osprey-release
testing
VerifiedTrustedCommunity
Guides a maintainer through cutting an OSPREY release on the GitHub Flow workflow: open a version-bump PR, merge it to main, tag the merge commit, push the tag, verify the automated PyPI publish. Use when someone says "create a release", "bump the version", "cut v2026.X.Y", "publish to PyPI", "tag a release", or asks about the release process. Composes with `osprey-contribute` for the bump PR. Versions follow CalVer (vYYYY.M.P) and the source of truth is `src/osprey/__init__.py` — Hatch derives the pyproject.toml version dynamically.
56SKILL.mdUpdated May 6, 2026
als-apg/osprey-pre-commit
development
VerifiedTrustedCommunity
Validates code before committing using OSPREY's three-tier check scripts. Runs linting, formatting, and tests to catch issues early. Use when ready to commit, before pushing, before opening a PR, or when the user asks to run checks, validate, or verify their changes. For the full contribution journey (branching, commits, push, PR, merge), use `osprey-contribute` instead — this skill is the focused validation step.
56SKILL.mdUpdated May 6, 2026
als-apg/osprey-contribute
development
VerifiedTrustedCommunity
Guides a contributor through the OSPREY GitHub Flow contribution journey from a working-tree change to a merged PR on main. Use when someone says "I want to contribute X to osprey", "help me commit/push this", "prep this branch for a PR", "open a PR", "my CI is failing on this branch", "rebase onto main", or wants help following the contributing workflow. Auto-detects whether they have push access to als-apg/osprey or are contributing from a fork. Composes with the osprey-pre-commit, commit-organize, and osprey-release skills — invoke this whenever someone is contributing code to OSPREY, even if they haven't named the workflow explicitly.
56SKILL.mdUpdated May 6, 2026