python deploy

DevOps Community

Skill notes

Pre-flight checks

!git status --short !git log --oneline -5 Deploy to: $ARGUMENTS If $ARGUMENTS is empty, stop immediately. Report: "No environment specified. Invoke as: /python-deploy <environment> (e.g., /python-deploy staging or /python-deploy production)."

Step 1: Abort if there are uncommitted changes

Check the git status output above. If it shows any lines (modified, untracked, staged, or deleted files), stop here. Report: "Deploy aborted: there are uncommitted changes. Commit or stash them before deploying to $ARGUMENTS." A clean working tree shows no output from git status --short. Do not proceed unless the output is empty.

Step 2: Run the test suite

Run: If any tests fail, report the failing test names and count, then stop. Do not proceed. If pytest is not installed, try: If neither is available, report that no test runner was found and stop. Do not deploy without running tests.

Step 3: Build the distribution package

Run: This requires the build package. If it is not installed, run: Then retry python -m build. If the build fails, report the error output and stop. On success, confirm the output: the dist/ directory should contain a .whl and a .tar.gz file.

Step 4: Create a deployment tag

Construct the tag name: Use current UTC date and time. Example: deploy-staging-20260513-143207. Run:

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
DevOps
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@tomevault-io · no license declared
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
Python
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1: Abort if there are uncommitted changes

Check the git status output above. If it shows any lines (modified, untracked, staged, or deleted files), stop here. Report: "Deploy aborted: there are uncommitted changes. Commit or stash them before deploying to $ARGUMENTS." A clean working tree shows no output from `git status --short`. Do not proceed unless the output is empty.

02
Step 2: Run the test suite

Run: If any tests fail, report the failing test names and count, then stop. Do not proceed. If pytest is not installed, try: If neither is available, report that no test runner was found and stop. Do not deploy without running tests.

03
Step 3: Build the distribution package

Run: This requires the `build` package. If it is not installed, run: Then retry `python -m build`. If the build fails, report the error output and stop. On success, confirm the output: the `dist/` directory should contain a `.whl` and a `.tar.gz` file.

04
Step 4: Create a deployment tag

Construct the tag name: Use current UTC date and time. Example: `deploy-staging-20260513-143207`. Run:

05
Step 5: Push the tag

Run: If the push fails, report the error and stop.

06
Step 6: Report success

Print a final summary: Source: davila7/claude-with-skills — distributed by TomeVault.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.