Safety check

Skill codecraftersautomation/claude-code/plugins/ccp/skills/safety-check

Claude Code plugins, MCP servers & skills by CodeCrafters Automation. Includes Change Claude Profile (ccp): hand off / take over work between Claude Code profiles (claude-team ⇄ claude-max) and keep their plugins in sync.

Install

npx -y skills add codecraftersautomation/claude-code --skill safety-check

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
0 stars0 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.

What its author says it does

Copied from the file, not written here

Check whether it's safe to hand off or take over by scanning the working tree for risky conditions. Use when the user asks "is it safe to switch/hand off", "any blockers", "check for secrets/conflicts before I switch profiles", or before/after /ccp:handoff and /ccp:takeover. Runs the git safety script and reports repo status, staged/unstaged/untracked/deleted files, merge conflicts, large files, likely secret files, and likely secrets in the diff. Writes .claude/ccp/handoff/SAFETY_CHECK.md.

SKILL.md

1.9 KB, 361 tokens by cl100k_base, as published. Nobody here has run it

CCP: safety-check

Decide whether the current repo state is safe to hand off or take over. This is a fast, read-only gate that surfaces the conditions most likely to cause data loss or a secret leak when switching profiles.

Steps

Run the safety script:
```
bash "${CLAUDE_PLUGIN_ROOT}/scripts/git-safety-check.sh"
```
(If the path differs in this install, find git-safety-check.sh under the CCP plugin's scripts/ directory.)
It writes .claude/ccp/handoff/SAFETY_CHECK.md covering:
- Is this a git repo? Current branch.
- Staged changes
- Unstaged (modified, tracked) changes
- Untracked files
- Deleted files
- Merge conflicts
- Large files (> 1 MB) in pending changes
- Likely secret files by name (.env, *.pem, id_rsa, .credentials.json, etc.)
- Likely secrets inside the diff (counted via the conservative redactor)
Summarize the verdict for the user: safe / proceed-with-caution / not-safe-yet, and list the specific things to address first (e.g. "resolve the merge conflict in app.ts", "untracked .env is in the changeset — exclude it").

Read-only

This skill inspects only. It never stages, commits, deletes, or installs anything.

What this skill must never do

Never switch accounts or touch credentials/OAuth/Keychain data.
Never install plugins.
Never print a discovered secret's value — locations and counts only.