safe-pr

name	safe-pr
description	Use this skill whenever Claude needs to create a feature branch, commit a batch of repo changes, push it, and open a GitHub PR while preventing financial statements, transaction exports, verification artifacts, or local trading profile files from being staged.

Safe PR

This workflow publishes harness changes without leaking financial data.

Steps

1. Inspect branch and repo state:
   • git status --short --branch
   • git remote -v
   • detect the base branch, preferring origin/main.
2. Confirm there are changes to publish. Stop if the only changes are ignored financial data.
3. Create or switch to a feature branch:
   • If on main or master, create agent/<short-summary>-YYYYMMDD-HHMM.
   • If already on a feature branch, continue only after confirming it is the intended branch.
4. Stage only harness files:
   • .claude/**
   • CLAUDE.md
   • README.md
   • .gitignore
   • .gitattributes
   • .gitkeep placeholders
5. Before committing, run:
   • git diff --cached --name-only
   • git diff --cached --check
   • git status --ignored --short
6. Refuse to proceed if any staged path is inside statements/, work/, or exports/ other than .gitkeep, or if any staged path is trading.MD.
7. Commit with a concise message, push the feature branch, and open a PR against main using gh pr create.

Notes

• Never use force push unless the user explicitly asks.
• Never add ignored files with git add -f.
• Include a PR summary of harness changes and a data-safety note.