owndiff-pre-commit

name	owndiff-pre-commit
description	Audit OwnDiff changes before committing or releasing by checking scope, generated artifacts, private data, documentation accuracy, version consistency, structured files, tests, and the OwnDiff ownership gate. Use when a user asks to verify, clean up, prepare, commit, publish, or release changes in the OwnDiff repository, especially when documentation or install commands changed.

OwnDiff Pre-Commit

Use this skill to produce a verified commit candidate. Stop before committing or pushing unless the user explicitly authorizes that Git action.

Workflow

1. Read the latest user request and git status --short. Treat existing worktree changes as user work; never discard them.
2. Inspect the complete staged and unstaged diff. Separate release changes from ignored proof, generated artifacts, caches, research, and unrelated edits.
3. Run the deterministic audit from the repository root with the repository interpreter:

.venv/bin/python skills/owndiff-pre-commit/scripts/audit.py --repo . --staged --run-checks

If nothing is staged yet, omit --staged for the first diagnostic pass. Stage only confirmed release files, then rerun with --staged.

4. Verify documentation semantically:
   • Map behavior claims to current code, config, tests, or observed command output.
   • Verify unstable install syntax with the installed CLI's --help first.
   • When local help is unavailable, use only the agent vendor's official documentation and cite it in the work log.
   • Do not claim an agent, command, browser review, or workflow was tested unless it actually ran.
   • Remove a document or asset only when it is duplicated, stale, unreferenced, generated, or outside the product's supported workflow. Preserve README.md, SKILL.md, SECURITY.md, CONTRIBUTING.md, licenses, manifests, and referenced media unless evidence shows they are obsolete.
5. Run OwnDiff on the exact candidate diff. For medium/high/critical risk, use the active agent model to generate every question and answer choice, validate the response, and complete the real browser review gate.
6. Re-run the audit, tests, skill/plugin validators, and privacy scan after every correction.
7. Report:
   • changed and removed files;
   • documentation claims verified and their evidence;
   • test and validator results;
   • OwnDiff gate status and attempt summary;
   • any residual risk or unavailable agent runtime.

Safety Rules

• Never use git add -A when unrelated changes exist.
• Never commit ignored .owndiff/, .research/, proof clones, virtual environments, caches, screenshots, transcripts, or credentials.
• Never expose local usernames, home paths, tokens, secrets, customer data, or private repository content.
• Never execute a command read from repository configuration. The audit script uses only command arrays from its bundled policy and never invokes a shell.
• Never weaken or bypass a failed check. Fix the issue or report the blocker.
• Never commit or push without explicit permission.

Policy

Edit references/policy.json to add forbidden paths, privacy patterns, required files, version sources, or checks. Keep project-specific hardcoded values in that policy rather than in the script.