[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72WJGD6T865T8NH8SA4XYKP":3,"skill-same:01M72WJGD6T865T8NH8SA4XYKP":76},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"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":28,"commitSha":29,"skillDirectory":30,"forksCount":31,"repositoryHtmlUrl":26,"repositoryHomepageUrl":32,"ownerHtmlUrl":33,"ownerBlogUrl":32,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M72WJGD6T865T8NH8SA4XYKP","pr-logbook",null,"Composes PR titles and bodies, logbook entries and a PR's squash-merge message, and marks a spec implemented in its PR. Use when opening or updating a PR, logging to an issue, writing a PR squash-merge message, or flipping a spec to implemented. Not for local commit messages.","crewrig\u002Fcrewrig","crewrig","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F283580446?v=4","01M72WDBD9H0YW5JBHNZ0TEVWB","01M72WDBEBNRBAS94AXRPEVYNK",24,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fcrewrig\u002Fcrewrig\u002Fblob\u002Fmain\u002F.gemini\u002Fskills\u002Fpr-logbook\u002FSKILL.md",[],[],"2026-11-10 22:39:42",false,"---\nname: pr-logbook\ndescription: \"Composes PR titles and bodies, logbook entries and a PR's squash-merge message, and marks a spec implemented in its PR. Use when opening or updating a PR, logging to an issue, writing a PR squash-merge message, or flipping a spec to implemented. Not for local commit messages.\"\nlicense: Apache-2.0\ncompatibility: \"Requires Node.js 24 (scripts run as node scripts\u002F\u003Cname>.ts), git, and the forge CLI (gh for GitHub, glab for GitLab, tea for Gitea).\"\nmetadata:\n  provenance:\n    canonical: \"https:\u002F\u002Fgithub.com\u002Fcrewrig\u002Fcrewrig\"\n    feedback: \"https:\u002F\u002Fgithub.com\u002Fcrewrig\u002Fcrewrig\"\n    version: \"1.6.0\"\n---\n\n\n# PR & Logbook Composer\n\nTurns a finished change into a PR a reviewer can read in under five\nminutes, and a logbook entry the next agent can pick up cold. Mechanical\nchecks live in bundled scripts; you supply the judgement.\n\n## Scripts\n\nRun `node \u003Cskill-dir>\u002Fscripts\u002F\u003Cname>.ts` from wherever the input files are;\npaths you pass stay relative to your current directory. Each takes `--json` for a machine-readable\nresult and exits `0` (ok), `1` (finding), `2` (usage error) or `3`\n(precondition failed). Conventions shared by all scripts are in\n[`references\u002Fscript-contract.md`](references\u002Fscript-contract.md).\n\n| When | Command | Exit `1` means |\n|---|---|---|\n| After drafting a title and body, before opening or editing the PR | `node scripts\u002Flint-pr-body.ts --title-file \u003Cfile> --body-file \u003Cfile>` (add `--title-style gitmoji` when the project uses Gitmoji; `--template \u003Cfile>` when it has its own body template) | A rule is broken: title over 70 characters or ending in a period, a missing, duplicated or misordered section, an empty preamble, or a CI skip directive. Fix the draft and rerun until clean. |\n| Before writing the logbook entry | `node scripts\u002Fresolve-logbook-target.ts --body-file \u003Cfile>` | Never used. Read `data.mode`: `feature-issue` means comment on `data.issue`; `standalone` means create a logbook issue with the `logbook` label. |\n| When the PR implements a spec, before it merges | `node scripts\u002Fflip-spec-status.ts \u003Cspec-file>` (use `--dry-run` to preview) | The spec has a status other than `approved` or `implemented`. Stop and tell the orchestrator; do not edit the status by hand. |\n\nExit `2` or `3` means the call or the environment is wrong, not the draft.\nFix the invocation; do not work around it by skipping the script.\n\n## Workflow\n\n### 1. Read the project's conventions\n\nRead the project's `AGENTS.md` (or equivalent) for the required PR\nsections, the commit-message convention, the logbook label and location,\nand any branch or merge-method rules. The same crew serves repositories\nwith different rules, so an assumed convention is usually a wrong one. If\nthe project defines its own body template, pass it to the linter.\n\n### 2. Compose title and body\n\n- Title: imperative, states what changed (the body carries why). Use the\n  project's emoji or prefix convention.\n- Body: start from `assets\u002Fpr-body.template.md`, or the project's own.\n  Write the purpose in two sentences for a human, a reading order that\n  points at the load-bearing files and non-obvious decisions, a test plan\n  covering the golden path and one failure mode, and a walkthrough for\n  agents that states what was added, changed and removed, and why.\n- On a bug-type issue that folds related bugs, give the folded-bugs entry\n  each item with its status; otherwise write \"not applicable\".\n- Write both to files and run `lint-pr-body.ts`. Open or edit the PR only\n  once it exits `0`.\n\n### 3. Logbook entry\n\nRun `resolve-logbook-target.ts` on the final body. A feature issue is its\nown logbook, so comment on it through the forge CLI\n(`gh issue comment \u003Cissue> --body ...`). Do not add the `logbook` label to a pre-existing feature issue.\nOnly a PR with no feature issue gets a standalone logbook issue, created\nwith `gh issue create ... --label logbook`. Forge access is CLI-only.\n\nA logbook is the record the next agent reads to avoid your mistakes, not\na status update. Use this shape and append, never rewrite; a reverted\nwrong turn still belongs in the log:\n\n```markdown\n### YYYY-MM-DD — \u003Cone-line topic>\n\n**Context**: \u003Cwhat task or PR this entry attaches to>\n\n**What was tried**: \u003Cdecision or experiment>\n\n**Outcome**: \u003Cgreen \u002F red \u002F partial, with a link to evidence>\n\n**Lesson**: \u003Cthe durable insight, in one sentence>\n```\n\nWhen folded bugs exist, the next stage-transition comment carries one\nbullet per folded item (symptom, the step that exposed it, status), a\nbullet for the final sweep, and one per bug filed elsewhere. The closure\ncomment lists each item's resolution.\n\n### 4. Squash-merge message\n\nWhen the project squash-merges, this message is what survives in `git\nlog`, so make it denser than the PR description rather than a paste of it:\n\n```text\n\u003Cconvention prefix> \u003Cimperative title> (#\u003Cpr-number>)\n\n\u003Cone paragraph: what the PR delivered, in the past tense>\n\n\u003Cone paragraph: why, the constraint or motivation behind it>\n\n\u003Cbullets for significant follow-ups, if any>\n```\n\nWrite the first paragraph in the past tense: the message records a change\nalready made. \"Added retries to the sync client\", not \"Adds retries to the\nsync client\" or \"The sync client now retries\".\n\nThe `#` reference is the forge-native one: GitHub and Gitea use `#`, GitLab\nuses `!` (`(!\u003Cmr-number>)`).\n\n### 5. Spec status flip\n\nIf the PR implements a spec, run `flip-spec-status.ts` on the spec file\non the implementation branch before merge, then record it in a new commit\n(not an amend), and push it when the PR branch is pushed, unless the user\nor the task says not to. The spec then lands on the main branch already\nmarked implemented. The script changes the status line only; any other\nedit to the spec does not belong in this change.\n\nA spec PR is opened as a draft and marked ready after its approval flip\nis pushed.\n\n### 6. Before pushing: executable bits\n\nText-only file writes silently drop the executable bit. If the diff\ntouches executable files, check `git ls-files --stage -- \u003Cfile>` shows\n`100755`, not `100644`. Restore with `git update-index --chmod=+x \u003Cfile>`\nand record it in a new commit, as with the spec flip.\n\n### 7. After merge\n\nClose the logbook issue through the forge CLI with reason completed,\nunless the entry went on a feature issue, in which case closing that issue\nis enough. Verify a feature issue named by a closing keyword really closed\ninstead of assuming the forge auto-closed it.\n\n## Version bumps\n\nA PR whose diff changes a skill or agent source must bump\n`metadata.provenance.version` in the same diff, because CI rejects the PR\notherwise. Use PATCH for wording fixes, MINOR for additive changes and\nMAJOR for breaking contract changes.\n\u003C!-- crewrig-repo-only:start -->\nCrewRig repository only: run `task check-skill-versions` to check locally.\n\u003C!-- crewrig-repo-only:end -->\n\n## Single writer per forge artifact\n\nConcurrent edits to one PR body or issue silently lose updates, so each\nartifact has one writer.\n\n- Your role owns what it creates. Opening a PR makes `pr-logbook` the\n  writer of its body; say so once on a `**Writer:**` line in the logbook\n  entry.\n- Do not rewrite another role's body or comment; route the change through\n  its writer. A new comment is always fine, since you own it.\n- A handover only counts when it comes from the current writer.\n- Observe immediately before writing: record the last-modification marker\n  (`gh pr view \u003Cn> --json updatedAt`, or the `glab`\u002F`tea` equivalent).\n- `gh pr edit` reports success even on a lost update. If the artifact\n  moved between your observation and your write, say so on the logbook.\n- When telling anyone what an artifact says, base it on a fresh\n  observation and quote its marker.\n\n## Grounding\n\nEvery technical claim (file counts, line counts, assertion lists, pass\ndeltas, exit codes, CI step names, invariants such as \"idempotent\") needs a\nverifiable source: a path with line range, a command output, or a sentence\nfrom your brief. Without one, write \"see diff\" or omit it; never estimate.\nRe-read the draft once before returning and strip any number or invariant\nyou cannot trace, since a fabricated claim that reaches a reviewer is\ncostly.\n\n## Output hygiene\n\nEvery tool result stays in context and is re-read on each later call.\n\n- Query `gh` with `--json` and `--jq` fields, never the full payload.\n- `tail` or `grep` logs down to the failing lines.\n- Read files by line range, never a whole spec.\n- Run `git diff --stat` before reading hunks.\n\n## Output\n\nWrite in the project's primary language (check `AGENTS.md`), as Markdown\nthat renders on the PR platform, with no emoji in the body unless the\nproject's convention uses them.\n\n## Friction reporting\n\nWhen something in this workflow misleads or blocks you, use the\n`harness-report` skill to tag it.\n\n## Idle behavior\n\nWhen re-activated after going idle with no new assignment, confirm\navailability in one sentence. Do not re-summarize a completed task.\n\nExample: \"Task #2 (logbook + PR for #N) is already completed — available for new work.\"\n\n## Shutdown protocol\n\nWhen the team lead sends a `shutdown_request` message, respond\nimmediately with `shutdown_response` (approve: true) and stop:\n\n```json\n{\"type\": \"shutdown_response\", \"request_id\": \"\u003Cid from request>\", \"approve\": true}\n```\n\nDo not defer, summarize completed tasks, or wait for an ongoing\noperation. The shutdown_request is a hard stop signal — the team lead\nhas confirmed all work is done.\n\nAfter completing a task and reporting to the team lead, do not start\nany further processing or re-enter a wait loop. Mark the task as\ncompleted via `TaskUpdate`, send the completion message, and then stop.\nThe team lead will send the next assignment or the shutdown signal.\n","# PR & Logbook Composer\n\nTurns a finished change into a PR a reviewer can read in under five\nminutes, and a logbook entry the next agent can pick up cold. Mechanical\nchecks live in bundled scripts; you supply the judgement.\n\n## Scripts\n\nRun `node \u003Cskill-dir>\u002Fscripts\u002F\u003Cname>.ts` from wherever the input files are;\npaths you pass stay relative to your current directory. Each takes `--json` for a machine-readable\nresult and exits `0` (ok), `1` (finding), `2` (usage error) or `3`\n(precondition failed). Conventions shared by all scripts are in\n[`references\u002Fscript-contract.md`](references\u002Fscript-contract.md).\n\n| When | Command | Exit `1` means |\n|---|---|---|\n| After drafting a title and body, before opening or editing the PR | `node scripts\u002Flint-pr-body.ts --title-file \u003Cfile> --body-file \u003Cfile>` (add `--title-style gitmoji` when the project uses Gitmoji; `--template \u003Cfile>` when it has its own body template) | A rule is broken: title over 70 characters or ending in a period, a missing, duplicated or misordered section, an empty preamble, or a CI skip directive. Fix the draft and rerun until clean. |\n| Before writing the logbook entry | `node scripts\u002Fresolve-logbook-target.ts --body-file \u003Cfile>` | Never used. Read `data.mode`: `feature-issue` means comment on `data.issue`; `standalone` means create a logbook issue with the `logbook` label. |\n| When the PR implements a spec, before it merges | `node scripts\u002Fflip-spec-status.ts \u003Cspec-file>` (use `--dry-run` to preview) | The spec has a status other than `approved` or `implemented`. Stop and tell the orchestrator; do not edit the status by hand. |\n\nExit `2` or `3` means the call or the environment is wrong, not the draft.\nFix the invocation; do not work around it by skipping the script.\n\n## Workflow\n\n### 1. Read the project's conventions\n\nRead the project's `AGENTS.md` (or equivalent) for the required PR\nsections, the commit-message convention, the logbook label and location,\nand any branch or merge-method rules. The same crew serves repositories\nwith different rules, so an assumed convention is usually a wrong one. If\nthe project defines its own body template, pass it to the linter.\n\n### 2. Compose title and body\n\n- Title: imperative, states what changed (the body carries why). Use the\n  project's emoji or prefix convention.\n- Body: start from `assets\u002Fpr-body.template.md`, or the project's own.\n  Write the purpose in two sentences for a human, a reading order that\n  points at the load-bearing files and non-obvious decisions, a test plan\n  covering the golden path and one failure mode, and a walkthrough for\n  agents that states what was added, changed and removed, and why.\n- On a bug-type issue that folds related bugs, give the folded-bugs entry\n  each item with its status; otherwise write \"not applicable\".\n- Write both to files and run `lint-pr-body.ts`. Open or edit the PR only\n  once it exits `0`.\n\n### 3. Logbook entry\n\nRun `resolve-logbook-target.ts` on the final body. A feature issue is its\nown logbook, so comment on it through the forge CLI\n(`gh issue comment \u003Cissue> --body ...`). Do not add the `logbook` label to a pre-existing feature issue.\nOnly a PR with no feature issue gets a standalone logbook issue, created\nwith `gh issue create ... --label logbook`. Forge access is CLI-only.\n\nA logbook is the record the next agent reads to avoid your mistakes, not\na status update. Use this shape and append, never rewrite; a reverted\nwrong turn still belongs in the log:\n\n```markdown\n### YYYY-MM-DD — \u003Cone-line topic>\n\n**Context**: \u003Cwhat task or PR this entry attaches to>\n\n**What was tried**: \u003Cdecision or experiment>\n\n**Outcome**: \u003Cgreen \u002F red \u002F partial, with a link to evidence>\n\n**Lesson**: \u003Cthe durable insight, in one sentence>\n```\n\nWhen folded bugs exist, the next stage-transition comment carries one\nbullet per folded item (symptom, the step that exposed it, status), a\nbullet for the final sweep, and one per bug filed elsewhere. The closure\ncomment lists each item's resolution.\n\n### 4. Squash-merge message\n\nWhen the project squash-merges, this message is what survives in `git\nlog`, so make it denser than the PR description rather than a paste of it:\n\n```text\n\u003Cconvention prefix> \u003Cimperative title> (#\u003Cpr-number>)\n\n\u003Cone paragraph: what the PR delivered, in the past tense>\n\n\u003Cone paragraph: why, the constraint or motivation behind it>\n\n\u003Cbullets for significant follow-ups, if any>\n```\n\nWrite the first paragraph in the past tense: the message records a change\nalready made. \"Added retries to the sync client\", not \"Adds retries to the\nsync client\" or \"The sync client now retries\".\n\nThe `#` reference is the forge-native one: GitHub and Gitea use `#`, GitLab\nuses `!` (`(!\u003Cmr-number>)`).\n\n### 5. Spec status flip\n\nIf the PR implements a spec, run `flip-spec-status.ts` on the spec file\non the implementation branch before merge, then record it in a new commit\n(not an amend), and push it when the PR branch is pushed, unless the user\nor the task says not to. The spec then lands on the main branch already\nmarked implemented. The script changes the status line only; any other\nedit to the spec does not belong in this change.\n\nA spec PR is opened as a draft and marked ready after its approval flip\nis pushed.\n\n### 6. Before pushing: executable bits\n\nText-only file writes silently drop the executable bit. If the diff\ntouches executable files, check `git ls-files --stage -- \u003Cfile>` shows\n`100755`, not `100644`. Restore with `git update-index --chmod=+x \u003Cfile>`\nand record it in a new commit, as with the spec flip.\n\n### 7. After merge\n\nClose the logbook issue through the forge CLI with reason completed,\nunless the entry went on a feature issue, in which case closing that issue\nis enough. Verify a feature issue named by a closing keyword really closed\ninstead of assuming the forge auto-closed it.\n\n## Version bumps\n\nA PR whose diff changes a skill or agent source must bump\n`metadata.provenance.version` in the same diff, because CI rejects the PR\notherwise. Use PATCH for wording fixes, MINOR for additive changes and\nMAJOR for breaking contract changes.\n\u003C!-- crewrig-repo-only:start -->\nCrewRig repository only: run `task check-skill-versions` to check locally.\n\u003C!-- crewrig-repo-only:end -->\n\n## Single writer per forge artifact\n\nConcurrent edits to one PR body or issue silently lose updates, so each\nartifact has one writer.\n\n- Your role owns what it creates. Opening a PR makes `pr-logbook` the\n  writer of its body; say so once on a `**Writer:**` line in the logbook\n  entry.\n- Do not rewrite another role's body or comment; route the change through\n  its writer. A new comment is always fine, since you own it.\n- A handover only counts when it comes from the current writer.\n- Observe immediately before writing: record the last-modification marker\n  (`gh pr view \u003Cn> --json updatedAt`, or the `glab`\u002F`tea` equivalent).\n- `gh pr edit` reports success even on a lost update. If the artifact\n  moved between your observation and your write, say so on the logbook.\n- When telling anyone what an artifact says, base it on a fresh\n  observation and quote its marker.\n\n## Grounding\n\nEvery technical claim (file counts, line counts, assertion lists, pass\ndeltas, exit codes, CI step names, invariants such as \"idempotent\") needs a\nverifiable source: a path with line range, a command output, or a sentence\nfrom your brief. Without one, write \"see diff\" or omit it; never estimate.\nRe-read the draft once before returning and strip any number or invariant\nyou cannot trace, since a fabricated claim that reaches a reviewer is\ncostly.\n\n## Output hygiene\n\nEvery tool result stays in context and is re-read on each later call.\n\n- Query `gh` with `--json` and `--jq` fields, never the full payload.\n- `tail` or `grep` logs down to the failing lines.\n- Read files by line range, never a whole spec.\n- Run `git diff --stat` before reading hunks.\n\n## Output\n\nWrite in the project's primary language (check `AGENTS.md`), as Markdown\nthat renders on the PR platform, with no emoji in the body unless the\nproject's convention uses them.\n\n## Friction reporting\n\nWhen something in this workflow misleads or blocks you, use the\n`harness-report` skill to tag it.\n\n## Idle behavior\n\nWhen re-activated after going idle with no new assignment, confirm\navailability in one sentence. Do not re-summarize a completed task.\n\nExample: \"Task #2 (logbook + PR for #N) is already completed — available for new work.\"\n\n## Shutdown protocol\n\nWhen the team lead sends a `shutdown_request` message, respond\nimmediately with `shutdown_response` (approve: true) and stop:\n\n```json\n{\"type\": \"shutdown_response\", \"request_id\": \"\u003Cid from request>\", \"approve\": true}\n```\n\nDo not defer, summarize completed tasks, or wait for an ongoing\noperation. The shutdown_request is a hard stop signal — the team lead\nhas confirmed all work is done.\n\nAfter completing a task and reporting to the team lead, do not start\nany further processing or re-enter a wait loop. Mark the task as\ncompleted via `TaskUpdate`, send the completion message, and then stop.\nThe team lead will send the next assignment or the shutdown signal.\n",{"name":5,"license":14,"metadata":23,"description":7,"compatibility":27},{"provenance":24},{"version":25,"feedback":26,"canonical":26},"1.6.0","https:\u002F\u002Fgithub.com\u002Fcrewrig\u002Fcrewrig","Requires Node.js 24 (scripts run as node scripts\u002F\u003Cname>.ts), git, and the forge CLI (gh for GitHub, glab for GitLab, tea for Gitea).","main","6d7f2262eb86a02d21a60a8147ed6f8a27d7b8eb",".gemini\u002Fskills\u002Fpr-logbook",6,"https:\u002F\u002Fcrewrig.org","https:\u002F\u002Fgithub.com\u002Fcrewrig","This is the organisation behind the crewrig framework","2026-11-15 04:46:08",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add crewrig\u002Fcrewrig --skill pr-logbook",{"tool":42,"command":43},"bunx","bunx skills add crewrig\u002Fcrewrig --skill pr-logbook",{"tool":45,"command":46},"pnpm","pnpm dlx skills add crewrig\u002Fcrewrig --skill pr-logbook","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcrewrig\u002Fcrewrig\u002Fblob\u002Fmain\u002F.gemini\u002Fskills\u002Fpr-logbook\u002FSKILL.md",true,[50,56,62,68,72],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"assets\u002Fpr-body.template.md","ASSET","资产文件",788,"https:\u002F\u002Fgithub.com\u002Fcrewrig\u002Fcrewrig\u002Fblob\u002Fmain\u002F.gemini\u002Fskills\u002Fpr-logbook\u002Fassets\u002Fpr-body.template.md",{"path":57,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Fscript-contract.md","REFERENCE","参考文档",2517,"https:\u002F\u002Fgithub.com\u002Fcrewrig\u002Fcrewrig\u002Fblob\u002Fmain\u002F.gemini\u002Fskills\u002Fpr-logbook\u002Freferences\u002Fscript-contract.md",{"path":63,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":66,"sourceHtmlUrl":67},"scripts\u002Fflip-spec-status.ts","SCRIPT","脚本",5082,"https:\u002F\u002Fgithub.com\u002Fcrewrig\u002Fcrewrig\u002Fblob\u002Fmain\u002F.gemini\u002Fskills\u002Fpr-logbook\u002Fscripts\u002Fflip-spec-status.ts",{"path":69,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":70,"sourceHtmlUrl":71},"scripts\u002Flint-pr-body.ts",11538,"https:\u002F\u002Fgithub.com\u002Fcrewrig\u002Fcrewrig\u002Fblob\u002Fmain\u002F.gemini\u002Fskills\u002Fpr-logbook\u002Fscripts\u002Flint-pr-body.ts",{"path":73,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":74,"sourceHtmlUrl":75},"scripts\u002Fresolve-logbook-target.ts",5729,"https:\u002F\u002Fgithub.com\u002Fcrewrig\u002Fcrewrig\u002Fblob\u002Fmain\u002F.gemini\u002Fskills\u002Fpr-logbook\u002Fscripts\u002Fresolve-logbook-target.ts",[77,85,90,95,100,105],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":84},"01M76AJKRKGGYZFJJHKE32Q5ZZ","fixture","Fixture skill. Mentions scripts\u002Ffrontmatter-only.ts which must be ignored.","https:\u002F\u002Fgithub.com\u002Fcrewrig\u002Fcrewrig\u002Fblob\u002Fmain\u002Fscripts\u002Ftests\u002Ffixtures\u002Fskill-scripts-citations\u002Fyaml-example\u002FSKILL.md",[],[],"2026-11-12 13:55:43",{"skillNo":86,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":84},"01M76AJJHS0AHW5HJJQCVVJ4DH","https:\u002F\u002Fgithub.com\u002Fcrewrig\u002Fcrewrig\u002Fblob\u002Fmain\u002Fscripts\u002Ftests\u002Ffixtures\u002Fskill-scripts-citations\u002Funterminated\u002FSKILL.md",[],[],{"skillNo":91,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":84},"01M76AJH8VJ2NAE000285J1D8F","https:\u002F\u002Fgithub.com\u002Fcrewrig\u002Fcrewrig\u002Fblob\u002Fmain\u002Fscripts\u002Ftests\u002Ffixtures\u002Fskill-scripts-citations\u002Funresolved\u002FSKILL.md",[],[],{"skillNo":96,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":84},"01M76AJG4M862QH00H5QVVT60P","https:\u002F\u002Fgithub.com\u002Fcrewrig\u002Fcrewrig\u002Fblob\u002Fmain\u002Fscripts\u002Ftests\u002Ffixtures\u002Fskill-scripts-citations\u002Fstray\u002FSKILL.md",[],[],{"skillNo":101,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":84},"01M76AJEZKZVMWZXCKXCFNQQ6B","https:\u002F\u002Fgithub.com\u002Fcrewrig\u002Fcrewrig\u002Fblob\u002Fmain\u002Fscripts\u002Ftests\u002Ffixtures\u002Fskill-scripts-citations\u002Fresolving\u002FSKILL.md",[],[],{"skillNo":106,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":84},"01M76AJD4G4K2YK2SMN8NSEG9R","https:\u002F\u002Fgithub.com\u002Fcrewrig\u002Fcrewrig\u002Fblob\u002Fmain\u002Fscripts\u002Ftests\u002Ffixtures\u002Fskill-scripts-citations\u002Freferences-unfenced\u002FSKILL.md",[],[]]