Pmo git safety

Skill witchwasin/Axiom-PMO/skills/pmo-git-safety

Use for branch, diff, sensitive file, commit, push, tag, and release safety.From its SKILL.md

Install

npx -y skills add witchwasin/Axiom-PMO --skill pmo-git-safety

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

2 stars2 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

1.7 KB, as published. Nobody here has run it

pmo-git-safety

Purpose

Keep git operations reviewable, intentional, and safe.

Trigger

Use before commit, push, tag, branch changes, release publication, or when sensitive files may be present.

Required Inputs

Current branch, git status, diff summary, validation output, human approval state, and git/release permissions from pmo-config/policy.json.

Allowed Context

Read git metadata and changed files needed for review. Do not inspect denied secret files.

Mode Behavior

Use pmo-config/policy.json for git mutation and production release permission requirements. Lite, Standard, and Strict all require human confirmation for commit/push/tag; push requires explicit per-push confirmation.

Execution Steps

Confirm branch and remote.
Summarize staged/unstaged/untracked changes.
Check sensitive filenames and denied paths.
Confirm tests and human review before commit.
Never push until explicitly approved.

Output Contract

Return branch, account/remote if requested, changed files, test result, and pending human actions.

Approval Rules

Commit is local only after per-round diff approval. Push/PR/merge require final explicit approval. Production release approval cannot be automated.

Validation Command

node cli/axiom.mjs check

Prohibited Actions

Do not use destructive git commands, force push, bypass permissions, approve production release, push without explicit per-push confirmation, or commit unrelated user changes.

Completion Criteria

Working tree changes are intentional, tests are green, no sensitive files are included, and human approval is recorded.