swain-update

仓库: cristoslc/swain
安装量: 59
排名: #12568

安装

npx skills add https://github.com/cristoslc/swain --skill swain-update

Update Swain Update the local installation of swain skills to the latest version, then reconcile governance configuration. Step 1 — Detect current installation Check whether .claude/skills/ contains any swain- directories: ls -d .claude/skills/swain- 2

/dev/null If no swain skill directories are found, inform the user this appears to be a fresh install rather than an update, then continue anyway — the steps below work for both cases. Step 2 — Backup local modifications Before overwriting skill directories, check for user modifications that should be preserved. Detect modified files Compare local skill files against the installed version's git origin:

Create a temporary reference copy

tmp

$( mktemp -d ) git clone --depth 1 https://github.com/cristoslc/swain.git " $tmp /swain" 2

/dev/null

Find locally modified files

modified_files

( ) for skill_dir in .claude/skills/swain-*/ ; do skill_name = $( basename " $skill_dir " ) ref_dir = " $tmp /swain/skills/ $skill_name " [ -d " $ref_dir " ] || continue while IFS = read -r file ; do rel = " ${file

$skill_dir} " ref_file = " $ref_dir / $rel " if [ -f " $ref_file " ] ; then if ! diff -q " $file " " $ref_file "

/dev/null 2

&1 ; then modified_files += ( " $file " ) fi else

File exists locally but not in upstream — user-added file

modified_files += ( " $file " ) fi done < < ( find " $skill_dir " -type f ) done Backup modified files If modified files are found: Create a backup directory: .agents/update-backup// Copy each modified file preserving directory structure Inform the user: "Found N locally modified files — backed up to .agents/update-backup// " List the modified files If no modified files are found, skip and continue. The reference clone from this step can be reused as the fallback source in Step 3. Step 3 — Detect installed agent platforms Before installing, detect which agent platforms are present on the system. This avoids creating dotfolder stubs for every supported platform (see GitHub issue #21 ). Read the agent-to-directory mapping from references/agent-platforms.json in this skill's directory. For each entry in the agents map, expand the path (replace ~ with $HOME , evaluate env var defaults) and check whether the directory exists: detected_agents = ( )

claude-code is always included (we're running inside it)

detected_agents += ( "claude-code" )

Check each platform's config directory

[
[
-d
"
${
HOME
}
/.cursor"
]
]
&&
detected_agents
+=
(
"cursor"
)
[
[
-d
"
${
HOME
}
/.codeium/windsurf"
]
]
&&
detected_agents
+=
(
"windsurf"
)
[
[
-d
"
${CODEX_HOME
:-
${
HOME
}
/.codex}"
]
]
&&
detected_agents
+=
(
"codex"
)
[
[
-d
"
${
HOME
}
/.cline"
]
]
&&
detected_agents
+=
(
"cline"
)
[
[
-d
"
${
HOME
}
/.continue"
]
]
&&
detected_agents
+=
(
"continue"
)
[
[
-d
"
${
HOME
}
/.augment"
]
]
&&
detected_agents
+=
(
"augment"
)
[
[
-d
"
${XDG_CONFIG_HOME
:-
${
HOME
}
/.config}/goose"
]
]
&&
detected_agents
+=
(
"goose"
)
[
[
-d
"
${
HOME
}
/.roo"
]
]
&&
detected_agents
+=
(
"roo"
)
[
[
-d
"
${
HOME
}
/.gemini"
]
]
&&
detected_agents
+=
(
"gemini-cli"
)
[
[
-d
"
${
HOME
}
/.copilot"
]
]
&&
detected_agents
+=
(
"github-copilot"
)
[
[
-d
"
${XDG_CONFIG_HOME
:-
${
HOME
}
/.config}/amp"
]
]
&&
detected_agents
+=
(
"amp"
)
[
[
-d
"
${XDG_CONFIG_HOME
:-
${
HOME
}
/.config}/opencode"
]
]
&&
detected_agents
+=
(
"opencode"
)
[
[
-d
"
${
HOME
}
/.kiro"
]
]
&&
detected_agents
+=
(
"kiro"
)
Build the
-a
flags from detected agents:
agent_flags
=
""
for
agent
in
"
${detected_agents
[
@
]
}
"
;
do
agent_flags
=
"
$agent_flags
-a
$agent
"
done
Tell the user which platforms were detected:
Detected N agent platform(s): claude-code, codex, gemini-cli, ...
Step 4 — Update via npx
Run the skills package manager with only the detected agents:
npx skills
add
cristoslc/swain
$agent_flags
-s
'*'
-y
This installs all skills (
-s '*'
) for only the detected platforms, skipping confirmation (
-y
). No dotfolder stubs are created for platforms that aren't installed.
If
npx
fails (command not found, network error, or non-zero exit), fall back to a direct git clone:
tmp
=
$(
mktemp
-d
)
git
clone
--depth
1
https://github.com/cristoslc/swain.git
"
$tmp
/swain"
cp
-r
"
$tmp
/swain/skills/"
* .claude/skills/
rm
-rf
"
$tmp
"
Step 5 — Reconcile governance
Invoke the
swain-doctor
skill. This validates governance rules, cleans up legacy skill directories (including any renamed in this release), repairs
.beads/.gitignore
, and untracks any runtime files that leaked into git. The skill is idempotent, so running it after every update is always safe.
Step 6 — Restore guidance
If files were backed up in Step 2:
List the backed-up files with their paths
For each, explain the situation:
User-added config files
(e.g.,
config/yazi/yazi.toml
): Suggest moving to
.agents/config//
or
swain.settings.json
where they'll survive future updates
Patched scripts
Show the diff between the backup and the new version. If the upstream version includes the fix, confirm the patch is no longer needed. If not, offer to re-apply the patch. Remind the user: "To avoid this in future, store customizations in .agents/config/ or swain.settings.json — these survive updates." Step 7 — Report List the installed swain skill directories and extract each skill's version from its SKILL.md frontmatter: for skill in .claude/skills/swain-/SKILL.md ; do name = $( grep '^name:' " $skill " | head -1 | sed 's/name: //' ) version = $( grep 'version:' " $skill " | head -1 | sed 's/.version: //' ) echo " $name v $version " done Show the user the list and confirm the update is complete. If backups were created in Step 2, also show: "Backed up N modified files to .agents/update-backup// . See Step 5 for restore guidance."
← 返回排行榜