[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CQB6BGQJSRC1SBE84S5V74":3,"skill-same:01M7CQB6BGQJSRC1SBE84S5V74":43},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":13,"repositoryHtmlUrl":26,"repositoryHomepageUrl":6,"ownerHtmlUrl":27,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":28,"install":29,"resources":42},"01M7CQB6BGQJSRC1SBE84S5V74","work-record",null,"Use when you finished work on a tracker task and it must be recorded in the workspace through a merge request.","maximk777\u002Fopencode-config","maximk777","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F205286132?v=4","01M7CQ4VVPFQ3MDCXJBFB0HPTZ","01M7CQ4VWA2GG0H2CNNREZ9AN9",0,"MIT","https:\u002F\u002Fgithub.com\u002Fmaximk777\u002Fopencode-config\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fnormalize-team\u002F.agents\u002Fskills\u002Fwork-record\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: work-record\ndescription: Use when you finished work on a tracker task and it must be recorded in the workspace through a merge request.\n---\n# Record finished work\n\n## Steps\n1. Go to the workspace root: the nearest directory, walking up from where you are, where `test -f .agents\u002Fkit.json` succeeds. Run every command below from there.\n2. Ask the person for the task id. Below the id is `\u003CID>`. Check it:\n   - Read `id_pattern` from `tracker\u002Ftracker.json`. JSON doubles every backslash, so `\\\\d` in the file means `\\d`.\n   - Rewrite the pattern for `grep -E`: write every `\\d` as `[0-9]`, because `grep -E` does not know `\\d`.\n   - Run `printf '%s\\n' '\u003CID>' | grep -Ex '\u003Crewritten pattern>'`. The `-x` makes the whole id match, not a part of it.\n   - If it prints nothing, stop and ask again.\n3. Read `.local\u002Fdrafts\u002F\u003CID>.md`. If it does not exist, ask the person four questions: what changed, which decisions were taken, what is still open, and what was verified. Wait for the answers before going on.\n4. Find the workspace default branch: run `git symbolic-ref --short refs\u002Fremotes\u002Forigin\u002FHEAD` and remove the `origin\u002F` prefix; when the command fails, use `main`. Call it `\u003Cdefault>`. Then run `git fetch origin`.\n5. Read the manifest of the default branch: run `git show origin\u002F\u003Cdefault>:repos.json`. Below, \"the manifest\" is this output, never the `repos.json` file of the current branch: the record is checked against the default branch, and a repository added only on an unmerged branch would fail the `work-record` check. Collect commits. For each entry in `repositories` of the manifest whose directory `repos\u002F\u003Cname>` exists, with `\u003Cdefault_branch>` from the entry:\n   - Run `git -C repos\u002F\u003Cname> fetch --prune`.\n   - Run `git -C repos\u002F\u003Cname> for-each-ref --format='%(refname:short)' refs\u002Fheads refs\u002Fremotes | grep -E '(^|[^A-Za-z0-9])\u003CID>([^0-9]|$)'`. Each printed line is one `\u003Cbranch>`, used as printed. The grep keeps only names where `\u003CID>` is a whole token, so `TASK-1` does not match `feat\u002FTASK-10-y`.\n   - For every `\u003Cbranch>`, run `git -C repos\u002F\u003Cname> log --format=%H origin\u002F\u003Cdefault_branch>..\u003Cbranch>`.\n   - Run `git -C repos\u002F\u003Cname> log --format=%H -E --grep='\u003CID>([^0-9]|$)' origin\u002F\u003Cdefault_branch>` to find work that is already merged.\n   - Write each sha as `\u003Cname>@\u003Csha>`. Keep each value once, in the order found.\n   - A repository with at least one sha goes into `repos`.\n6. If no repository gave a sha, ask the person which repositories and branches hold the work, and repeat step 5 for them. A repository that is not in the manifest cannot go into `repos`; tell the person it must be merged into `\u003Cdefault>` first.\n7. Collect merge requests. For each repository in `repos`, look at its `forge` in the manifest:\n   - `gitlab`: if `command -v glab` and `glab auth status` both succeed, run `glab mr list --search \"\u003CID>\" --all --output json` inside `repos\u002F\u003Cname>` and take every `web_url` value that contains `\u002F-\u002Fmerge_requests\u002F` (the other `web_url` values are user profiles). Otherwise add `glab` to the `missing` list.\n   - `github`: if `command -v gh` and `gh auth status` both succeed, run `gh pr list --search \"\u003CID>\" --state all --json url --jq \".[].url\"` inside `repos\u002F\u003Cname>` and take every printed URL. Otherwise add `gh` to the `missing` list.\n   - `git`: there is no merge request data; add nothing.\n   - Keep each URL once, in the order found. Keep each name in `missing` once.\n8. Run `git status --porcelain --untracked-files=no`. If it prints anything, stop and tell the person: the workspace has uncommitted tracked changes. Commit nothing.\n9. If `git rev-parse --verify --quiet work\u002F\u003CID>` or `git rev-parse --verify --quiet origin\u002Fwork\u002F\u003CID>` succeeds, the branch already exists:\n   - For each of `work\u002F\u003CID>` and `origin\u002Fwork\u002F\u003CID>` that exists, run `git diff --name-only origin\u002F\u003Cdefault>...\u003Cthat branch>`.\n   - If any printed path does not start with `work\u002F\u003CID>\u002F`, stop and tell the person which paths they are. Commit nothing.\n   - If `origin\u002Fwork\u002F\u003CID>` exists, the branch is already pushed. Its commits must never be rewritten. Remember this for steps 14 and 15. Then:\n     - When `git rev-parse --verify --quiet work\u002F\u003CID>` succeeds, run `git switch work\u002F\u003CID>`, then `git branch --set-upstream-to=origin\u002Fwork\u002F\u003CID>`.\n     - Otherwise run `git switch --track origin\u002Fwork\u002F\u003CID>`.\n     - Run `git pull --ff-only`. If it fails, stop and tell the person that the local and pushed `work\u002F\u003CID>` differ. Commit nothing.\n   - If only the local `work\u002F\u003CID>` exists, run `git switch work\u002F\u003CID>`.\n   - Bring the branch up to date: run `GIT_EDITOR=true git merge --no-edit origin\u002F\u003Cdefault>`. The branch may predate a repository merged into `\u003Cdefault>`; after the merge its `repos.json` equals the manifest from step 5, which step 12 checks the record against. The branch changes only `work\u002F\u003CID>\u002F`, so the merge is clean. On a conflict, run `git diff --name-only --diff-filter=U` to list the files, then `git merge --abort`, show the two versions as step 14 describes and stop. Commit nothing.\n   - Skip step 10.\n10. Otherwise run, one by one:\n    - `git switch \u003Cdefault>`\n    - `git pull --ff-only`\n    - `git switch -c work\u002F\u003CID>`\n11. Write `work\u002F\u003CID>\u002Frecord.md` from `.agents\u002Ftemplates\u002Fwork-record.md`:\n    - Frontmatter `task: \u003CID>`.\n    - `repos`, `merge_requests` and `commits` as block lists: the line `key:`, then one line `  - value` per value. Write `key: []` when the list is empty.\n    - Add `story:` only when the person names a story. Add `contract:` or `consumed_contract:` only when the person gives them, as `key:` then lines `  sub: value`.\n    - Replace `\u003Cone-line summary>` in the title with one line about the work.\n    - Fill `## Changed`, `## Decisions`, `## Open questions` and `## Verification` from the draft or the answers. Write \"None.\" in a section with nothing to say.\n    - Write a stand as a link to its key, `[stand:\u003Cname>](..\u002F..\u002Fenvironments.json)`, never as an address.\n    - Never link into `.local\u002F`.\n12. If `command -v python3` succeeds, check the record:\n    - Run `python3 tools\u002Fgenerate.py`, then `python3 tools\u002Fcheck.py`. Each finding is a line `path:line rule message`.\n    - If a finding has the path `work\u002F\u003CID>\u002Frecord.md`, fix it in that file and run both commands again.\n    - Exception: a `work-record` finding \"repository X is not in repos.json\" for a repository X taken from the manifest in step 5 is never fixed by removing X from `repos`. Stop and tell the person the finding. Commit nothing.\n    - Change no other file. When no finding has the path `work\u002F\u003CID>\u002Frecord.md`, stop repeating. Remember the findings that are left for the report.\n    - Otherwise, when `python3` is missing, remember the line `check not run: python3 missing`.\n13. Commit: run `git add work\u002F\u003CID>\u002F`, then `git commit -m \"docs(work): record \u003CID>\"`.\n14. Update from the default branch:\n    - If step 9 found `origin\u002Fwork\u002F\u003CID>`, run `GIT_EDITOR=true git merge --no-edit origin\u002F\u003Cdefault>`. On a conflict, run `git diff --name-only --diff-filter=U` to list the files, then `git merge --abort`.\n    - Otherwise run `git pull --rebase origin \u003Cdefault>`. On a conflict, run `git diff --name-only --diff-filter=U` to list the files, then `git rebase --abort`.\n    - A conflict means someone else changed `work\u002F\u003CID>\u002F`. For each listed `\u003Cfile>`, show the person two versions with their labels: \"default branch\" is the output of `git show origin\u002F\u003Cdefault>:\u003Cfile>`, and \"your branch\" is the output of `git show work\u002F\u003CID>:\u003Cfile>`. Then stop.\n15. Push and open the merge request by `params.forge` in `.agents\u002Fkit.json`:\n    - `gitlab`: run `git push -u origin work\u002F\u003CID> -o merge_request.create -o merge_request.title=\"Work record \u003CID>\"`.\n    - `github`: run `git push -u origin work\u002F\u003CID>`, then `gh pr create --title \"Work record \u003CID>\" --body \"work\u002F\u003CID>\u002Frecord.md\"`. If `gh` is missing or the command fails, print its error and ask the person to open the pull request for branch `work\u002F\u003CID>`.\n    - `git`: run `git push -u origin work\u002F\u003CID>`, print the branch name `work\u002F\u003CID>` and ask the person to open the merge request.\n    - Never push with `--force` or `--force-with-lease`.\n16. If the push is rejected, print the error and these commands to finish by hand, then stop:\n    - When step 9 found `origin\u002Fwork\u002F\u003CID>`: `git pull --no-rebase --no-edit origin work\u002F\u003CID>`, then `GIT_EDITOR=true git merge --no-edit origin\u002F\u003Cdefault>`.\n    - Otherwise: `git pull --rebase origin \u003Cdefault>`. After fixing a conflict, run `git add \u003Cfile>`, then `GIT_EDITOR=true git rebase --continue`.\n    - Then the push for the forge:\n      - `gitlab`: `git push -u origin work\u002F\u003CID> -o merge_request.create -o merge_request.title=\"Work record \u003CID>\"`\n      - `github`: `git push -u origin work\u002F\u003CID>`, then `gh pr create --title \"Work record \u003CID>\" --body \"work\u002F\u003CID>\u002Frecord.md\"`\n      - `git`: `git push -u origin work\u002F\u003CID>`, then open the merge request for branch `work\u002F\u003CID>` in the forge web page.\n17. Report to the person:\n    - the record path `work\u002F\u003CID>\u002Frecord.md`;\n    - the branch `work\u002F\u003CID>`;\n    - the merge request link, or the instruction to open it;\n    - `missing: \u003Cnames from the missing list, joined with \", \">`, or `missing: none`;\n    - the check findings left in other files, if any;\n    - as the last line, the check result, or `check not run: python3 missing`.\n\n## Example record\n`work\u002FTASK-1\u002Frecord.md` for work in repository `demo-bff` with one commit and no merge request data:\n\n```markdown\n---\ntask: TASK-1\nrepos:\n  - demo-bff\nmerge_requests: []\ncommits:\n  - demo-bff@2c0efd7072c42fb1df4dce53f4c284baf338a035\n---\n# TASK-1: Show the card limit on the payment screen\n\n## Changed\ndemo-bff: the `\u002Fpayments\u002Fscreen` response now has a `card_limit` field read from the limits service.\n\n## Decisions\nThe limit is cached for 60 seconds per card to keep the screen fast; the limits service allows this staleness.\n\n## Open questions\nNone.\n\n## Verification\nUnit tests pass in demo-bff. The payment screen was opened on [stand:test](..\u002F..\u002Fenvironments.json) and showed the limit for a test card.\n```\n\n## Without Python\n1. Skip `python3 tools\u002Fgenerate.py` and `python3 tools\u002Fcheck.py` in step 12.\n2. A work record changes no generated file, so no recipe is needed.\n3. End the report with the line:\n\ncheck not run: python3 missing\n","# Record finished work\n\n## Steps\n1. Go to the workspace root: the nearest directory, walking up from where you are, where `test -f .agents\u002Fkit.json` succeeds. Run every command below from there.\n2. Ask the person for the task id. Below the id is `\u003CID>`. Check it:\n   - Read `id_pattern` from `tracker\u002Ftracker.json`. JSON doubles every backslash, so `\\\\d` in the file means `\\d`.\n   - Rewrite the pattern for `grep -E`: write every `\\d` as `[0-9]`, because `grep -E` does not know `\\d`.\n   - Run `printf '%s\\n' '\u003CID>' | grep -Ex '\u003Crewritten pattern>'`. The `-x` makes the whole id match, not a part of it.\n   - If it prints nothing, stop and ask again.\n3. Read `.local\u002Fdrafts\u002F\u003CID>.md`. If it does not exist, ask the person four questions: what changed, which decisions were taken, what is still open, and what was verified. Wait for the answers before going on.\n4. Find the workspace default branch: run `git symbolic-ref --short refs\u002Fremotes\u002Forigin\u002FHEAD` and remove the `origin\u002F` prefix; when the command fails, use `main`. Call it `\u003Cdefault>`. Then run `git fetch origin`.\n5. Read the manifest of the default branch: run `git show origin\u002F\u003Cdefault>:repos.json`. Below, \"the manifest\" is this output, never the `repos.json` file of the current branch: the record is checked against the default branch, and a repository added only on an unmerged branch would fail the `work-record` check. Collect commits. For each entry in `repositories` of the manifest whose directory `repos\u002F\u003Cname>` exists, with `\u003Cdefault_branch>` from the entry:\n   - Run `git -C repos\u002F\u003Cname> fetch --prune`.\n   - Run `git -C repos\u002F\u003Cname> for-each-ref --format='%(refname:short)' refs\u002Fheads refs\u002Fremotes | grep -E '(^|[^A-Za-z0-9])\u003CID>([^0-9]|$)'`. Each printed line is one `\u003Cbranch>`, used as printed. The grep keeps only names where `\u003CID>` is a whole token, so `TASK-1` does not match `feat\u002FTASK-10-y`.\n   - For every `\u003Cbranch>`, run `git -C repos\u002F\u003Cname> log --format=%H origin\u002F\u003Cdefault_branch>..\u003Cbranch>`.\n   - Run `git -C repos\u002F\u003Cname> log --format=%H -E --grep='\u003CID>([^0-9]|$)' origin\u002F\u003Cdefault_branch>` to find work that is already merged.\n   - Write each sha as `\u003Cname>@\u003Csha>`. Keep each value once, in the order found.\n   - A repository with at least one sha goes into `repos`.\n6. If no repository gave a sha, ask the person which repositories and branches hold the work, and repeat step 5 for them. A repository that is not in the manifest cannot go into `repos`; tell the person it must be merged into `\u003Cdefault>` first.\n7. Collect merge requests. For each repository in `repos`, look at its `forge` in the manifest:\n   - `gitlab`: if `command -v glab` and `glab auth status` both succeed, run `glab mr list --search \"\u003CID>\" --all --output json` inside `repos\u002F\u003Cname>` and take every `web_url` value that contains `\u002F-\u002Fmerge_requests\u002F` (the other `web_url` values are user profiles). Otherwise add `glab` to the `missing` list.\n   - `github`: if `command -v gh` and `gh auth status` both succeed, run `gh pr list --search \"\u003CID>\" --state all --json url --jq \".[].url\"` inside `repos\u002F\u003Cname>` and take every printed URL. Otherwise add `gh` to the `missing` list.\n   - `git`: there is no merge request data; add nothing.\n   - Keep each URL once, in the order found. Keep each name in `missing` once.\n8. Run `git status --porcelain --untracked-files=no`. If it prints anything, stop and tell the person: the workspace has uncommitted tracked changes. Commit nothing.\n9. If `git rev-parse --verify --quiet work\u002F\u003CID>` or `git rev-parse --verify --quiet origin\u002Fwork\u002F\u003CID>` succeeds, the branch already exists:\n   - For each of `work\u002F\u003CID>` and `origin\u002Fwork\u002F\u003CID>` that exists, run `git diff --name-only origin\u002F\u003Cdefault>...\u003Cthat branch>`.\n   - If any printed path does not start with `work\u002F\u003CID>\u002F`, stop and tell the person which paths they are. Commit nothing.\n   - If `origin\u002Fwork\u002F\u003CID>` exists, the branch is already pushed. Its commits must never be rewritten. Remember this for steps 14 and 15. Then:\n     - When `git rev-parse --verify --quiet work\u002F\u003CID>` succeeds, run `git switch work\u002F\u003CID>`, then `git branch --set-upstream-to=origin\u002Fwork\u002F\u003CID>`.\n     - Otherwise run `git switch --track origin\u002Fwork\u002F\u003CID>`.\n     - Run `git pull --ff-only`. If it fails, stop and tell the person that the local and pushed `work\u002F\u003CID>` differ. Commit nothing.\n   - If only the local `work\u002F\u003CID>` exists, run `git switch work\u002F\u003CID>`.\n   - Bring the branch up to date: run `GIT_EDITOR=true git merge --no-edit origin\u002F\u003Cdefault>`. The branch may predate a repository merged into `\u003Cdefault>`; after the merge its `repos.json` equals the manifest from step 5, which step 12 checks the record against. The branch changes only `work\u002F\u003CID>\u002F`, so the merge is clean. On a conflict, run `git diff --name-only --diff-filter=U` to list the files, then `git merge --abort`, show the two versions as step 14 describes and stop. Commit nothing.\n   - Skip step 10.\n10. Otherwise run, one by one:\n    - `git switch \u003Cdefault>`\n    - `git pull --ff-only`\n    - `git switch -c work\u002F\u003CID>`\n11. Write `work\u002F\u003CID>\u002Frecord.md` from `.agents\u002Ftemplates\u002Fwork-record.md`:\n    - Frontmatter `task: \u003CID>`.\n    - `repos`, `merge_requests` and `commits` as block lists: the line `key:`, then one line `  - value` per value. Write `key: []` when the list is empty.\n    - Add `story:` only when the person names a story. Add `contract:` or `consumed_contract:` only when the person gives them, as `key:` then lines `  sub: value`.\n    - Replace `\u003Cone-line summary>` in the title with one line about the work.\n    - Fill `## Changed`, `## Decisions`, `## Open questions` and `## Verification` from the draft or the answers. Write \"None.\" in a section with nothing to say.\n    - Write a stand as a link to its key, `[stand:\u003Cname>](..\u002F..\u002Fenvironments.json)`, never as an address.\n    - Never link into `.local\u002F`.\n12. If `command -v python3` succeeds, check the record:\n    - Run `python3 tools\u002Fgenerate.py`, then `python3 tools\u002Fcheck.py`. Each finding is a line `path:line rule message`.\n    - If a finding has the path `work\u002F\u003CID>\u002Frecord.md`, fix it in that file and run both commands again.\n    - Exception: a `work-record` finding \"repository X is not in repos.json\" for a repository X taken from the manifest in step 5 is never fixed by removing X from `repos`. Stop and tell the person the finding. Commit nothing.\n    - Change no other file. When no finding has the path `work\u002F\u003CID>\u002Frecord.md`, stop repeating. Remember the findings that are left for the report.\n    - Otherwise, when `python3` is missing, remember the line `check not run: python3 missing`.\n13. Commit: run `git add work\u002F\u003CID>\u002F`, then `git commit -m \"docs(work): record \u003CID>\"`.\n14. Update from the default branch:\n    - If step 9 found `origin\u002Fwork\u002F\u003CID>`, run `GIT_EDITOR=true git merge --no-edit origin\u002F\u003Cdefault>`. On a conflict, run `git diff --name-only --diff-filter=U` to list the files, then `git merge --abort`.\n    - Otherwise run `git pull --rebase origin \u003Cdefault>`. On a conflict, run `git diff --name-only --diff-filter=U` to list the files, then `git rebase --abort`.\n    - A conflict means someone else changed `work\u002F\u003CID>\u002F`. For each listed `\u003Cfile>`, show the person two versions with their labels: \"default branch\" is the output of `git show origin\u002F\u003Cdefault>:\u003Cfile>`, and \"your branch\" is the output of `git show work\u002F\u003CID>:\u003Cfile>`. Then stop.\n15. Push and open the merge request by `params.forge` in `.agents\u002Fkit.json`:\n    - `gitlab`: run `git push -u origin work\u002F\u003CID> -o merge_request.create -o merge_request.title=\"Work record \u003CID>\"`.\n    - `github`: run `git push -u origin work\u002F\u003CID>`, then `gh pr create --title \"Work record \u003CID>\" --body \"work\u002F\u003CID>\u002Frecord.md\"`. If `gh` is missing or the command fails, print its error and ask the person to open the pull request for branch `work\u002F\u003CID>`.\n    - `git`: run `git push -u origin work\u002F\u003CID>`, print the branch name `work\u002F\u003CID>` and ask the person to open the merge request.\n    - Never push with `--force` or `--force-with-lease`.\n16. If the push is rejected, print the error and these commands to finish by hand, then stop:\n    - When step 9 found `origin\u002Fwork\u002F\u003CID>`: `git pull --no-rebase --no-edit origin work\u002F\u003CID>`, then `GIT_EDITOR=true git merge --no-edit origin\u002F\u003Cdefault>`.\n    - Otherwise: `git pull --rebase origin \u003Cdefault>`. After fixing a conflict, run `git add \u003Cfile>`, then `GIT_EDITOR=true git rebase --continue`.\n    - Then the push for the forge:\n      - `gitlab`: `git push -u origin work\u002F\u003CID> -o merge_request.create -o merge_request.title=\"Work record \u003CID>\"`\n      - `github`: `git push -u origin work\u002F\u003CID>`, then `gh pr create --title \"Work record \u003CID>\" --body \"work\u002F\u003CID>\u002Frecord.md\"`\n      - `git`: `git push -u origin work\u002F\u003CID>`, then open the merge request for branch `work\u002F\u003CID>` in the forge web page.\n17. Report to the person:\n    - the record path `work\u002F\u003CID>\u002Frecord.md`;\n    - the branch `work\u002F\u003CID>`;\n    - the merge request link, or the instruction to open it;\n    - `missing: \u003Cnames from the missing list, joined with \", \">`, or `missing: none`;\n    - the check findings left in other files, if any;\n    - as the last line, the check result, or `check not run: python3 missing`.\n\n## Example record\n`work\u002FTASK-1\u002Frecord.md` for work in repository `demo-bff` with one commit and no merge request data:\n\n```markdown\n---\ntask: TASK-1\nrepos:\n  - demo-bff\nmerge_requests: []\ncommits:\n  - demo-bff@2c0efd7072c42fb1df4dce53f4c284baf338a035\n---\n# TASK-1: Show the card limit on the payment screen\n\n## Changed\ndemo-bff: the `\u002Fpayments\u002Fscreen` response now has a `card_limit` field read from the limits service.\n\n## Decisions\nThe limit is cached for 60 seconds per card to keep the screen fast; the limits service allows this staleness.\n\n## Open questions\nNone.\n\n## Verification\nUnit tests pass in demo-bff. The payment screen was opened on [stand:test](..\u002F..\u002Fenvironments.json) and showed the limit for a test card.\n```\n\n## Without Python\n1. Skip `python3 tools\u002Fgenerate.py` and `python3 tools\u002Fcheck.py` in step 12.\n2. A work record changes no generated file, so no recipe is needed.\n3. End the report with the line:\n\ncheck not run: python3 missing\n",{"name":5,"description":7},"main","84be7f584d7d6998f014342de57ee511e9596cd2","tests\u002Ffixtures\u002Fnormalize-team\u002F.agents\u002Fskills\u002Fwork-record","https:\u002F\u002Fgithub.com\u002Fmaximk777\u002Fopencode-config","https:\u002F\u002Fgithub.com\u002Fmaximk777","2026-10-30 20:22:07",{"source":8,"skillName":5,"commands":30,"prompt":40,"zipAvailable":41},[31,34,37],{"tool":32,"command":33},"npx","npx skills add maximk777\u002Fopencode-config --skill work-record",{"tool":35,"command":36},"bunx","bunx skills add maximk777\u002Fopencode-config --skill work-record",{"tool":38,"command":39},"pnpm","pnpm dlx skills add maximk777\u002Fopencode-config --skill work-record","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmaximk777\u002Fopencode-config\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fnormalize-team\u002F.agents\u002Fskills\u002Fwork-record\u002FSKILL.md",true,[],[44,51,56,63,70,77],{"skillNo":45,"name":46,"nameZh":6,"description":47,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":48,"categories":49,"keywords":50,"publishedAt":18},"01M7CQCJ5WYEQM6E1T0RDVKWAY","verify","Use when a change in __SERVICE__ must be checked before review","https:\u002F\u002Fgithub.com\u002Fmaximk777\u002Fopencode-config\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fworkspace-repo-kits\u002Fkit-1.1.0\u002Ffiles\u002Fskills\u002Fverify\u002FSKILL.md",[],[],{"skillNo":52,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":18},"01M7CQCG5MCSNDNS98TGAGXP7E","https:\u002F\u002Fgithub.com\u002Fmaximk777\u002Fopencode-config\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fnormalize-team\u002F.claude\u002Fskills\u002Fwork-record\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":18},"01M7CQCDGQBT2GXCKQAC1B5R0R","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.","https:\u002F\u002Fgithub.com\u002Fmaximk777\u002Fopencode-config\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fnormalize-team\u002F.claude\u002Fskills\u002Ftask-new\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":18},"01M7CQC93WN986EY48RFPZHZM7","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.","https:\u002F\u002Fgithub.com\u002Fmaximk777\u002Fopencode-config\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fnormalize-team\u002F.claude\u002Fskills\u002Ftask-decompose\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":18},"01M7CQC5FZQWPTBK0J0FHWS513","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.","https:\u002F\u002Fgithub.com\u002Fmaximk777\u002Fopencode-config\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fnormalize-team\u002F.claude\u002Fskills\u002Ftask-context\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":18},"01M7CQC1Q2YECCM2N9TPJAAJQA","repos-sync","Use to update clones of your repositories under repos\u002F and see their branch, lag and uncommitted changes.","https:\u002F\u002Fgithub.com\u002Fmaximk777\u002Fopencode-config\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fnormalize-team\u002F.claude\u002Fskills\u002Frepos-sync\u002FSKILL.md",[],[]]