How do I install the Set Repo Managed skill?

Run npx skillmds@latest add christian289/set-repo-managed in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Set Repo Managed safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: CAUTION, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Set Repo Managed?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Set Repo Managed free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Set Repo Managed?

christian289 (@christian289) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Set Repo Managed by christian289 — Agent Skill

Name: Set Repo Managed
Author: christian289

Set Repo Managed

Sets the server-managed 'Managed' flag in ~/.wpf-dev-pack-mcp/state.json. Managed=true lets WpfDevPackMcp git reset --hard its clone to origin/<branch> on refresh (only safe for a dedicated clone the server owns); Managed=false makes refresh non-destructive (ff-only when clean, skip when dirty) — required when repoPath is your active working repo. Use to stop the MCP from resetting your working tree, or to hand a dedicated clone back to server management.

christian289 Updated Sep 21, 2026

File contents

Set WpfDevPackMcp Managed Flag

Sets Managed in ~/.wpf-dev-pack-mcp/state.json (preserving LastPullUtc). This flag decides how the server refreshes the clone at repoPath.

If $0 is empty, use AskUserQuestion to ask for true or false. Do NOT proceed until a value is provided.

dotnet "${CLAUDE_PLUGIN_ROOT}/scripts/SetWpfDevPackManaged.cs" "$0"

What it controls (mcp/Git/RepoRefresher.cs):

true — on refresh the server runs git fetch + git reset --hard origin/<branch> on repoPath. Use ONLY for a dedicated clone the server created/owns. Never set true when repoPath is your active working repo — a refresh will discard uncommitted changes and reset the branch to origin/<branch>, destroying local work.
false — refresh is non-destructive: git pull --ff-only when the tree is clean, skip when dirty. Use when repoPath points at your own working clone.

Surface the output verbatim. Inspect the current flag with /wpf-dev-pack:show-wpf-dev-pack-config.

Frequently asked questions