set-repo-branch — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited set-repo-branch (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Sets the branch field in ~/.wpf-dev-pack-mcp/config.json — the branch the MCP server fetches/serves WPF knowledge from — leaving repoPath unchanged.
If `$0` is empty, use AskUserQuestion to ask which branch to track (e.g., `main`). Do NOT proceed until a branch is provided.
dotnet "${CLAUDE_PLUGIN_ROOT}/scripts/SetWpfDevPackBranch.cs" "$0"Surface the output verbatim, including any ! warning (e.g. repoPath not set yet → run /wpf-dev-pack:set-repo-path first). The new branch takes effect on the next WpfDevPackMcp refresh.
WhenManaged=true(see/wpf-dev-pack:set-repo-managed), refresh hard-resets the clone toorigin/<branch>, so the branch must exist on the remote. View the current branch with/wpf-dev-pack:show-wpf-dev-pack-config.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.