repo-kit-install
Use to install the repository kit named in a repos.json entry into your local clone of that repository, on a new branch, without committing.
- License 许可
- MIT
- 最近更新
- 2026-10-30
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- repo-kit-install
- description
- Use to install the repository kit named in a repos.json entry into your local clone of that repository, on a new branch, without committing.
03 SKILL.md 正文
Install a repository kit
This skill writes into the clone repos/<name>, never into the workspace. In the clone it writes only under .agents/, the .agent/ links it repairs in step 13, and the one AGENTS.md line of step 17. It never reads .env files, .local/env or secret values, never prints tokens, and never commits or pushes.
Words used below
<ws>: the workspace root, an absolute path (the output ofpwdin step 1).<name>: the repository name inrepos.json.<clone>:<ws>/repos/<name>.<kind>:kit.kindof the entry.<kitdir>:<ws>/.agents/repo-kits/<kind>.<version>:versionin<kitdir>/kit.json. This is the workspace version of the kit; the workspace's own.agents/kit.jsonis a different file.<branch>:repo-kit-<kind>-<version>, for examplerepo-kit-example-0.1.0.<default>:default_branchof the entry.<out>: a temporary folder for the rendered kit, outside the clone and the workspace.<base>: the folder the clone's kit files are read from. It is<clone>/.agentwhile<clone>/.agentsdoes not exist and<clone>/.agentdoes; otherwise it is<clone>/.agents. The kit path.agents/<p>is the clone file<base>/<p>.<sha256>:shasum -a 256whencommand -v shasumprints a path, otherwisesha256sum.- States of a path:
absent,same,replaceable,edited,obsolete,removed-edited,foreign(see## Recipe: status). Decisions for aneditedpath:kit,local,raise, exactly these words.
Stops
Every stop prints its message and ends the skill. Before a stop in this table the skill has written nothing into the clone and created no branch. When <out> already exists, run rm -rf <out> before stopping. Only step 16 can stop after the clone changed; it prints the commands that discard the attempt.
| Stop | Message |
|---|---|
| S1 no digest tool | Stop: python3, shasum and sha256sum are all missing, so file digests cannot be computed. Nothing was changed. |
| S2 unknown repository | Stop: repository <name> is not in repos.json. Nothing was changed. |
| S3 invalid kit | Stop: the kit of repository <name> in repos.json is invalid: <reason>. Fix the entry or the kit through a workspace merge request, then run repo-kit-install again. Nothing was changed. |
| S4 render failed | Stop: rendering kit <kind> for repository <name> failed: <reason>. Nothing was changed. |
| S5 clone missing | Stop: clone repos/<name> is missing. Clone it with the repos-sync skill, then run repo-kit-install again. Nothing was changed. |
| S6 dirty clone | Stop: clone repos/<name> has uncommitted changes. Commit or stash them yourself, then run repo-kit-install again. Nothing was changed. |
| S7 not on the default branch | Stop: clone repos/<name> is on branch <current>, not <default>. Switch it to <default> yourself, then run repo-kit-install again. Nothing was changed. |
| S8 both folders | Stop: repos/<name> has both .agent/ and .agents/. Which one should stay? Merge them by hand in a separate merge request, then run repo-kit-install again. Nothing was changed. |
| S9 other kind | Stop: repos/<name>/.agents/kit.json has kind <stamp kind>, but repos.json names kind <kind>. Changing the kind of a repository is the owner's decision. Nothing was changed. |
| S10 workspace behind | Stop: repos/<name>/.agents/kit.json has version <stamp version>, newer than version <version> of kit <kind> in this workspace. The workspace is behind: update it from its default branch, then run the skill again. Nothing was changed. |
| S11 branch exists | Stop: branch <branch> already exists in repos/<name>. Finish or delete it, then run repo-kit-install again. Nothing was changed. |
| S12 value the recipe cannot render | Stop: parameter <NAME> of repository <name> has the value <value>, which the recipe without python3 cannot render. Run repo-kit-install where python3 is available. Nothing was changed. |
| S13 raise | Stop: <path> got the decision raise. Change kit <kind> in .agents/repo-kits/<kind>/ through a workspace merge request, then run repo-kit-install again. Nothing was changed. |
S8 also asks the maintainer the question in its message and waits for the answer; the skill does not merge the folders.
Steps
-
Go to the workspace root: the nearest directory, walking up from where you are, where
test -f .agents/kit.jsonsucceeds. Runpwd; its output is<ws>. Use the workspace default branch after the merge request with the kit and the entry is merged. Start every command below withcd <ws> &&orcd <clone> &&as shown. -
Find the tools. When
command -v python3prints a path, Python is present. Otherwise, when neithercommand -v shasumnorcommand -v sha256sumprints a path, stop with S1. Without Python, follow## Without Pythonin every step that names a recipe. -
Ask the person for
<name>when they did not give it. Read<ws>/repos.jsonand find the entry ofrepositorieswhosenameis<name>. With no such entry, stop with S2. -
Check the entry's
kit:- When the entry has no
kit, stop with S3 and the reasonthe entry has no kit. - When
test -d <kitdir>fails, stop with S3 and the reasonkit kind <kind> is not a folder under .agents/repo-kits/. - Read
<kitdir>/kit.json.kit.paramsof the entry must have exactly the names inparamsofkit.json, and every value must match the wholepatternof its parameter. Check a pattern with Python asrepos-addstep 2 does:PATTERN='<pattern>' VALUE='<value>' python3 -c 'import os, re, sys; sys.exit(0 if re.fullmatch(os.environ["PATTERN"], os.environ["VALUE"]) else 1)'; exit code 0 means it matches. Without Python runprintf '%s\n' '<value>' | grep -Ex -e '<pattern>'; exit code 0 means the whole value matches. In both commands write each'inside the quotes as'\''.grep -Esyntax covers the patterns kits use: character classes,.,*,+,?,{m,n},|and groups. When a pattern uses syntaxgrep -Edoes not support, such as\d,\w,\s,(?or a lazy*?, compare by reading instead. A value with a line break never matches. On a missing name, an extra name or a value that does not match, stop with S3 and name the parameter in the reason. - Remember
<version>fromversionin<kitdir>/kit.jsonand<default>from the entry.
- When the entry has no
-
Render the kit. Run
mktemp -d; its output is<out>.- With Python:
cd <ws> && python3 tools/repo_kit.py render <name> <out>. When it exits 2, stop with S4 and use its error line as the reason. - Without Python: apply
## Recipe: render.<out>/.agents/now holds every kit file with the placeholders replaced.
- With Python:
-
Check the clone:
- When
test -d <clone>/.gitfails, stop with S5. - When
cd <clone> && git status --porcelainprints anything, stop with S6. - When
cd <clone> && git rev-parse --abbrev-ref HEADprints something other than<default>, stop with S7 with that output as<current>. - When both
test -d <clone>/.agentandtest -d <clone>/.agentssucceed, stop with S8.
- When
-
Check for a stamp. When
test -f <clone>/.agents/kit.jsonsucceeds, the repository already has a kit:- Read
kindandversionfrom it (grep -m 1 '^ "kind": ' <clone>/.agents/kit.jsonandgrep -m 1 '^ "version": ' <clone>/.agents/kit.json). - When
kindis not<kind>, stop with S9. - Compare the stamp
versionwith<version>as three numbers, MAJOR first, then MINOR, then PATCH:1.10.0is newer than1.9.0. When the stamp version is newer, stop with S10. For example, stamp1.2.0and workspace kit1.1.0stop here. - Otherwise run
rm -rf <out>and continue with.agents/skills/repo-kit-update/SKILL.mdfor the same<name>from its first step. Do not run the rest of this skill.
- Read
-
When
cd <clone> && git rev-parse --verify --quiet refs/heads/<branch>orcd <clone> && git rev-parse --verify --quiet refs/remotes/origin/<branch>prints anything, stop with S11. -
Compare the clone with the kit.
- With Python:
cd <ws> && python3 tools/repo_kit.py status <name> repos/<name>. When it exits 2, stop with S4 and use its error line as the reason. - Without Python: apply
## Recipe: status. Each output line is<state> <path>. Before the folder move the paths still read.agents/...; the files behind them are under<base>. Without a stamp onlyabsent,same,editedandforeignoccur.
- With Python:
-
Collect decisions before writing anything. Show the person every
editedpath. For each path.agents/<p>, show the difference withdiff <base>/<p> <out>/.agents/<p>. When<base>is<clone>/.agent, show it with the old links normalized instead:LC_ALL=C sed 's#\.agent/#.agents/#g' <base>/<p> | diff - <out>/.agents/<p>. When thatdiffprints nothing, the file differs only in.agent/links, which step 13 repairs: tell the person so and write downkitfor the path without asking. Otherwise ask for one decision:kit: the clone file is replaced by the kit file; the clone text is lost.local: the clone text moves to.agents/local/<p>, and the kit file takes its place. Whentest -e <base>/local/<p>succeeds, that place is taken: tell the person and ask again forkitorraise.raise: the kit itself must change first. Write the decisions down as<decision> <path>. When the person gives any other word, ask again. When there is noeditedpath, there is nothing to ask.
-
When any path got
raise, runrm -rf <out>and stop with S13, naming that path. The clone has no new branch and no changed file. -
Create the branch:
cd <clone> && git switch -c <branch>. From here on the clone changes. -
Move the folder and repair links, only when
<base>is<clone>/.agent:cd <clone> && git mv .agent .agents. From now on<base>is<clone>/.agents.- List the lines that still link to the old folder:
cd <clone> && grep -rnI --exclude-dir=.git --exclude='.env' --exclude='.env.*' '\.agent/' .. Files named.envor.env.*are never read. - In every listed line change
.agent/to.agents/and change nothing else in the file. Remember the listed files outside.agents/for step 19. - Run the
grepof sub-step 2 again; it prints nothing.
This step runs before step 14, so text that step 14 moves to
.agents/local/under alocaldecision already has its.agent/links repaired. -
Apply the decisions, for each
editedpath.agents/<p>:kit:cd <clone> && cp <out>/.agents/<p> .agents/<p>.local:cd <clone> && mkdir -p "$(dirname .agents/local/<p>)" && mv .agents/<p> .agents/local/<p> && cp <out>/.agents/<p> .agents/<p>.
-
Copy every
absentpath.agents/<p>:cd <clone> && mkdir -p "$(dirname .agents/<p>)" && cp <out>/.agents/<p> .agents/<p>. Leavesamepaths as they are and do not touchforeignpaths. -
Write the stamp.
- With Python:
cd <ws> && python3 tools/repo_kit.py stamp <name> repos/<name>. - Without Python: apply
## Recipe: stamp. Then run step 9 again. Every kit path must now besame;foreignpaths stay. When another state is left, stop: runrm -rf <out>, tell the person every line whose state is neithersamenorforeign, and print these commands for the person to discard the attempt. Do not run them yourself:
cd <clone> && git reset --hard && git clean -fd cd <clone> && git switch <default> && git branch -d <branch>The first line removes every uncommitted change of this attempt, staged or untracked, including the folder move. The second returns the clone to
<default>and deletes<branch>. Step 6 made sure the clone had no uncommitted or untracked files before, so nothing else is lost. - With Python:
-
Check the root
AGENTS.mdof the clone. The clone owns it; the kit never rewrites it.cd <clone> && grep -n '\.agents/AGENTS\.md' AGENTS.mdandcd <clone> && grep -n '\.agents/local/' AGENTS.md. A command that prints a line means that link exists.- When both print a line, change nothing.
- Otherwise propose one line to the person, by what is missing, and add it as the last line of
AGENTS.mdonly when the person agrees. WhenAGENTS.mddoes not exist, propose creating it with only that line.
Write only the text after the label and the spaces.Both missing: Agent instructions: [.agents/AGENTS.md](.agents/AGENTS.md). Repository-only rules and skills: [.agents/local/](.agents/local/). Only .agents/local/: Repository-only rules and skills: [.agents/local/](.agents/local/). Only .agents/AGENTS.md: Agent instructions: [.agents/AGENTS.md](.agents/AGENTS.md). - When the line links to
.agents/local/andtest -d <clone>/.agents/localfails, runcd <clone> && mkdir -p .agents/local && touch .agents/local/.gitkeepso the link resolves.
-
List every
foreignpath from step 9. These files belong to the repository: do not move or change them. For each.agents/<p>proposegit mv .agents/<p> .agents/local/<p>to the person as a later change of their own. -
Run
rm -rf <out>. Print these commands for the person and do not run them. The repository's forge isforgeof the entry, not the forge of this workspace:cd <clone> git add -A .agents <files changed in step 13 outside .agents> <AGENTS.md when step 17 changed it> git commit -m "chore(agents): install kit <kind> <version>"Then, by
forge:gitlab:git push -u origin <branch> -o merge_request.create -o merge_request.title="Install kit <kind> <version>";github:git push -u origin <branch>, thengh pr create --fill;git:git push -u origin <branch>, then open the merge request by hand. Tell the person to adjust the commit message to the repository's own commit rules when it has them.
-
Report to the person:
<branch>; the decisions; the files copied; the files with repaired links; theAGENTS.mdline proposed or added; theforeignlist; the printed commands. Never commit or push yourself.
Example
Workspace entry payments-worker with kit example version 0.1.0 and "params": {"SERVICE": "payments-worker"}, forge gitlab, default branch main. The kit has files/AGENTS.md, files/rules/example.md and files/skills/example/SKILL.md. The clone repos/payments-worker is clean on main and has no .agents/, but has .agent/AGENTS.md equal to the rendered file, .agent/rules/example.md edited by hand, and .agent/notes.md. Its root AGENTS.md says See .agent/AGENTS.md.
- Step 9 prints:
same .agents/AGENTS.md foreign .agents/notes.md edited .agents/rules/example.md absent .agents/skills/example/SKILL.md - Step 10: the person decides
local .agents/rules/example.md. - Steps 12 to 16: branch
repo-kit-example-0.1.0;git mv .agent .agents; rootAGENTS.mdbecomesSee .agents/AGENTS.md.;.agents/rules/example.mdmoves to.agents/local/rules/example.mdand the kit file replaces it;.agents/skills/example/SKILL.mdis copied; the stamp is written as in## Recipe: stamp. Step 9 again printssamefor the three kit paths andforeign .agents/notes.md. - Step 17:
AGENTS.mdlinks to.agents/AGENTS.mdbut not to.agents/local/; the proposed line isRepository-only rules and skills: [.agents/local/](.agents/local/).The folder exists after thelocaldecision. - Step 18 proposes
git mv .agents/notes.md .agents/local/notes.md. - Step 19 prints
git add -A .agents AGENTS.md, the commit command andgit push -u origin repo-kit-example-0.1.0 -o merge_request.create -o merge_request.title="Install kit example 0.1.0".
Recipe: render
Gives exactly the files python3 tools/repo_kit.py render <name> <out> writes.
- Values. For every parameter in
paramsof<kitdir>/kit.json, take its value fromkit.paramsof the entry. The recipe replaces placeholders withsed, so it works only when no value contains/,&,\,",',__, a tab, a line break or another control character. For such a value stop with S12. - Placeholders. Run
cd <kitdir>/files && LC_ALL=C grep -rhoaE '__[A-Z][A-Z0-9_]*__' . | LC_ALL=C sort -u. Every printed line must be__<NAME>__for a<NAME>inparams. For any other line find the file withcd <kitdir>/files && LC_ALL=C grep -rlaF '<line>' .and stop with S4, reasonkit <kind>: files/<file> uses undeclared placeholder <NAME>. - Files. Kit files are every file under
<kitdir>/files/except files inside__pycache__folders. File names must not contain",\or control characters; otherwise stop with S12 naming the file instead of a parameter. Copy each filefiles/<p>to<out>/.agents/<p>, with onesedexpression-e 's/__<NAME>__/<value>/g'per parameter, in the order ofparams.LC_ALL=Cmakessedtreat the file as bytes, so line endings, a missing last newline and any encoding stay as they are:cd <kitdir>/files && LC_ALL=C find . -type f ! -path '*/__pycache__/*' | LC_ALL=C sort | while IFS= read -r p; do p=${p#./}; mkdir -p "<out>/.agents/$(dirname "$p")" && LC_ALL=C sed -e 's/__<NAME1>__/<value1>/g' -e 's/__<NAME2>__/<value2>/g' "$p" > "<out>/.agents/$p"; done
Example for kit example with the one parameter SERVICE = payments-worker, <kitdir> = <ws>/.agents/repo-kits/example and <out> = /tmp/tmp.k3Jd9:
cd <ws>/.agents/repo-kits/example/files && LC_ALL=C grep -rhoaE '__[A-Z][A-Z0-9_]*__' . | LC_ALL=C sort -u
prints only __SERVICE__, which is declared. Then:
cd <ws>/.agents/repo-kits/example/files && LC_ALL=C find . -type f ! -path '*/__pycache__/*' | LC_ALL=C sort | while IFS= read -r p; do p=${p#./}; mkdir -p "/tmp/tmp.k3Jd9/.agents/$(dirname "$p")" && LC_ALL=C sed -e 's/__SERVICE__/payments-worker/g' "$p" > "/tmp/tmp.k3Jd9/.agents/$p"; done
Result: /tmp/tmp.k3Jd9/.agents/AGENTS.md, /tmp/tmp.k3Jd9/.agents/rules/example.md and /tmp/tmp.k3Jd9/.agents/skills/example/SKILL.md. The first line of the rendered AGENTS.md is # payments-worker, and no rendered file contains __SERVICE__.
Recipe: status
Gives exactly the lines python3 tools/repo_kit.py status <name> repos/<name> prints. It needs <out> from ## Recipe: render. A digest is the first 64 characters of <sha256> run on the file as standard input: shasum -a 256 < <file> | cut -c 1-64. The stamp <clone>/.agents/kit.json is read as ## Recipe: stamp writes it: one files entry per line, "<path>": "<digest>". The stamp digest of a path is grep -F ' "<path>": "' <clone>/.agents/kit.json | head -n 1 | cut -d '"' -f 4; it is empty when there is no stamp or no such line.
For every rendered path .agents/<p>, the clone file F is <base>/<p>:
absent:Fdoes not exist;same:cmp -s <out>/.agents/<p> Fsucceeds;replaceable: otherwise, when the stamp digest of the path is not empty and equals the digest ofF;edited: otherwise.
For every path P in the stamp's files that is not rendered (test -f <out>/P fails), starts with .agents/, has no .. segment, and whose clone file <base>/<P without .agents/> exists:
obsolete: the stamp digest equals the digest of that file;removed-edited: otherwise. A stamp path whose clone file is missing prints nothing.
For every file under <base>, as the path .agents/<p>: foreign when it is not rendered, not a key in the stamp's files, not .agents/kit.json and not under .agents/local/.
Sort all lines by path, byte by byte. The commands, with the three values set in the first line:
OUT=<out>; CLONE=<clone>; BASE=<base>
STAMP="$CLONE/.agents/kit.json"
{
cd "$OUT" && LC_ALL=C find .agents -type f | while IFS= read -r P; do
F="$BASE/${P#.agents/}"
if [ ! -f "$F" ]; then echo "absent $P"
elif cmp -s "$P" "$F"; then echo "same $P"
else
H=$( [ -f "$STAMP" ] && grep -F " \"$P\": \"" "$STAMP" | head -n 1 | cut -d '"' -f 4 )
D=$(shasum -a 256 < "$F" | cut -c 1-64)
if [ -n "$H" ] && [ "$H" = "$D" ]; then echo "replaceable $P"; else echo "edited $P"; fi
fi
done
[ -f "$STAMP" ] && sed -n '/^ "files": {/,/^ }/p' "$STAMP" | grep '^ "' | while IFS= read -r L; do
P=$(printf '%s\n' "$L" | cut -d '"' -f 2); H=$(printf '%s\n' "$L" | cut -d '"' -f 4)
case "$P" in .agents/*) ;; *) continue ;; esac
case "/$P/" in */../*) continue ;; esac
[ -f "$OUT/$P" ] && continue
F="$BASE/${P#.agents/}"
[ -f "$F" ] || continue
if [ "$(shasum -a 256 < "$F" | cut -c 1-64)" = "$H" ]; then echo "obsolete $P"; else echo "removed-edited $P"; fi
done
[ -d "$BASE" ] && cd "$BASE" && LC_ALL=C find . -type f | while IFS= read -r p; do
P=".agents/${p#./}"
case "$P" in .agents/kit.json|.agents/local/*) continue ;; esac
[ -f "$OUT/$P" ] && continue
[ -f "$STAMP" ] && grep -qF " \"$P\": \"" "$STAMP" && continue
echo "foreign $P"
done
} | LC_ALL=C sort -k 2
Replace both shasum -a 256 with sha256sum when shasum is missing. The block runs the same in sh, bash and zsh.
Example: the clone of ## Example before the move, so BASE=<ws>/repos/payments-worker/.agent, no stamp, <out> from ## Recipe: render. .agent/AGENTS.md equals the rendered file, .agent/rules/example.md differs, .agent/skills/ does not exist, and .agent/notes.md is not a kit file. The lines are:
same .agents/AGENTS.md
foreign .agents/notes.md
edited .agents/rules/example.md
absent .agents/skills/example/SKILL.md
With a stamp holding the digest of the current .agent/rules/example.md, that line would be replaceable .agents/rules/example.md instead.
Recipe: stamp
Gives exactly the bytes of <clone>/.agents/kit.json that python3 tools/repo_kit.py stamp <name> repos/<name> writes. It needs <out> from ## Recipe: render, and the value rules of that recipe hold here too.
The file has these lines, each ending with a line break, and nothing else:
{"kind": "<kind>","version": "<version>","params": {- one line per parameter, in the order of
paramsin<kitdir>/kit.json:"<NAME>": "<value>", with a comma after every line except the last; },"files": {- one line per rendered file, sorted by path byte by byte:
".agents/<p>": "<digest of <out>/.agents/<p>>", with a comma after every line except the last; }}
A kit without parameters writes the single line "params": {}, instead of lines 4 to 6; a kit without files writes "files": {} instead of lines 7 to 9. This is how the tool prints an empty object.
The commands, with one argument per parameter line in the second printf. For a kit without parameters that line is printf '%s\n' ' "params": {},' instead. The files part needs no change: it prints "files": {} when <out> has no .agents/ files.
mkdir -p <clone>/.agents && cd <out> && {
printf '%s\n' '{' ' "kind": "<kind>",' ' "version": "<version>",'
printf '%s\n' ' "params": {' ' "<NAME1>": "<value1>",' ' "<NAME2>": "<value2>"' ' },'
FILES=$( [ -d .agents ] && LC_ALL=C find .agents -type f | LC_ALL=C sort | while IFS= read -r f; do printf ' "%s": "%s",\n' "$f" "$(shasum -a 256 < "$f" | cut -c 1-64)"; done | LC_ALL=C sed '$ s/,$//' )
if [ -n "$FILES" ]; then printf '%s\n' ' "files": {' "$FILES" ' }'; else printf '%s\n' ' "files": {}'; fi
printf '%s\n' '}'
} > <clone>/.agents/kit.json
Use sha256sum instead of shasum -a 256 when shasum is missing.
Example for ## Example, <out> = /tmp/tmp.k3Jd9:
mkdir -p <ws>/repos/payments-worker/.agents && cd /tmp/tmp.k3Jd9 && {
printf '%s\n' '{' ' "kind": "example",' ' "version": "0.1.0",'
printf '%s\n' ' "params": {' ' "SERVICE": "payments-worker"' ' },'
FILES=$( [ -d .agents ] && LC_ALL=C find .agents -type f | LC_ALL=C sort | while IFS= read -r f; do printf ' "%s": "%s",\n' "$f" "$(shasum -a 256 < "$f" | cut -c 1-64)"; done | LC_ALL=C sed '$ s/,$//' )
if [ -n "$FILES" ]; then printf '%s\n' ' "files": {' "$FILES" ' }'; else printf '%s\n' ' "files": {}'; fi
printf '%s\n' '}'
} > <ws>/repos/payments-worker/.agents/kit.json
The written repos/payments-worker/.agents/kit.json, with a line break after the last }:
{
"kind": "example",
"version": "0.1.0",
"params": {
"SERVICE": "payments-worker"
},
"files": {
".agents/AGENTS.md": "27ff1ccb6beb7cb7b873f3d9c173ff18e74fbb30572c299987bb09055b1d77b4",
".agents/rules/example.md": "e31c19605d14f680052c8bb7550bd2132105a0eacda42e9db2a11809743af543",
".agents/skills/example/SKILL.md": "777eb69778449f5ffa502dafaf1fee70914792262e0448e43a312adce57bd70b"
}
}
Without Python
- Step 2: without
python3, one ofshasumorsha256summust exist; with neither, stop with S1. - Step 4: check each value against its
patternwith thegrep -Excommand of step 4, or by reading when the pattern uses syntaxgrep -Edoes not support; the whole value must match. - Step 5: apply
## Recipe: renderinstead oftools/repo_kit.py render. - Steps 9 and 16: apply
## Recipe: statusinstead oftools/repo_kit.py status. - Step 16: apply
## Recipe: stampinstead oftools/repo_kit.py stamp. - The skill changes no workspace file, so there is no workspace check to run.
04 同仓库更多 Skills
verify
Use when a change in __SERVICE__ must be checked before review
work-record
Use when you finished work on a tracker task and it must be recorded in the workspace through a merge request.
task-new
Use to create one story in a stream from the stream profile's story template, link it from its scope screens and open a merge request.
task-decompose
Use to split a stream at the decomposition stage into stories - list scope screens without a story, create the accepted stories and close the stage through a merge request.
task-context
Use to gather the context of a story key or a tracker id - its story, stream stage, scope screens, repositories, decisions, mockups and work records.
repos-sync
Use to update clones of your repositories under repos/ and see their branch, lag and uncommitted changes.