[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B0TKFCTVQBTSNF9WF1MXJ6":3,"skill-same:01M7B0TKFCTVQBTSNF9WF1MXJ6":49},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":13,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":42},"01M7B0TKFCTVQBTSNF9WF1MXJ6","self-update-fix",null,"Fix a failing dependency update PR. Use when a self-update PR's CI fails, or when invoked by scripts\u002Fself-update-fix.sh.","gitricko\u002F.minions","gitricko","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F18060558?v=4","01M7B0KG9EHG0CZ0QT1EN5YPCR","01M7B0KGA0ZV14R7SKBF3B5SCT",2,"MIT","https:\u002F\u002Fgithub.com\u002Fgitricko\u002F.minions\u002Fblob\u002Fmain\u002Fskills\u002Fself-update-fix\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: self-update-fix\ndescription: Fix a failing dependency update PR. Use when a self-update PR's CI fails, or when invoked by scripts\u002Fself-update-fix.sh.\ndisable-model-invocation: true\n---\n\n# Fix a dependency update PR\n\nThis skill fixes a self-update PR whose CI has failed. The agent should not\nattempt to fix the PR if it involves touching `.github\u002Fworkflows\u002F`, as that is\noutside the scope of this skill and the D2 guardrail.\n\n## When to use this skill\n\nInvoke when a self-update PR (opened by the `self-update.yml` orchestrator) has\na failing CI check and the agent is expected to fix it. The skill is called\nfrom `scripts\u002Fself-update-fix.sh` with the PR number, the dependency name and\nversion, and the failed CI check name.\n\n## How to invoke this skill\n\nThe skill is invoked from `scripts\u002Fself-update-fix.sh` with four arguments:\n\n```\nscripts\u002Fself-update-fix.sh \u003CPR_NUMBER> \u003CDEP> \u003CVERSION> \u003CFAILED_CHECK>\n```\n\nThe agent should use the Hermes CLI or Pi CLI to interact with the PR and the\ndependency versions. Which CLI to use depends on the environment setup.\n\n### Example invocation (Hermes)\n\n```\nhermes fix-pr \u003CPR_NUMBER> --dep \u003CDEP> --version \u003CVERSION> --check \u003CFAILED_CHECK>\n```\n\n### Example invocation (Pi)\n\n```\npi -p fix-pr \u003CPR_NUMBER> --dep \u003CDEP> --version \u003CVERSION> --check \u003CFAILED_CHECK>\n```\n\n> The exact CLI command depends on the environment setup. The agent should use\n> the CLI that has access to the PR and dependency versions. If neither CLI is\n> available, the agent should report the failure and exit non-zero.\n\n## What the agent should do\n\nWhen invoked, the agent should perform the following steps:\n\n### 1. Checkout the PR branch\n\n> **Guardrail**: The agent must only checkout the PR branch. Do not check out\n> `main` or any other branch.\n\nThe PR branch can be checked out via the GitHub API or `git` commands. The\nagent should use the PR number to construct the branch name (typically\n`pr-${PR_NUMBER}` or similar).\n\n### 2. Read the CI failure\n\n> **Guardrail**: The agent must only read the CI failure output. Do not modify\n> CI configuration files.\n\nThe agent should:\n- Read the CI failure output from the PR's CI run\n- Understand which check failed and why\n- Note the failed dependency version and the error message\n\n### 3. Determine the fix\n\n> **Guardrail**: The agent must not modify `.github\u002Fworkflows\u002F` files. If the fix\n> requires changing CI configuration, stop and report to human.\n\nThe agent should determine what fix is needed based on the CI failure:\n\n- **Version bump issue**: If the bump was to a version that's incompatible, the\n  agent should revert to the previous version or adjust the version range.\n- **Config issue**: If the bump requires config changes (e.g., `.node-version`),\n  the agent should adjust the config file accordingly.\n- **Dependency issue**: If a dependency version is incompatible with others,\n  the agent should adjust the version range or pin the dependency.\n\n### 4. Apply the fix\n\nThe agent should edit the relevant files to fix the issue. The following files\nmay be edited:\n\n- `etc\u002Fdeps.yaml` — update the version field\n- `etc\u002Fversions.env` — update the version field (generated from deps.yaml)\n- `.node-version` — update the Node version\n- Other project files as needed (NOT `.github\u002Fworkflows\u002F`)\n\n### 5. Push the fix\n\nThe agent should push the fix to the PR branch:\n\n```\ngit checkout \u003CPR_BRANCH>\ngit add \u003Cedited_files>\ngit commit -m \"fix: \u003Cshort description of the fix>\"\ngit push origin \u003CPR_BRANCH>\n```\n\nThis will trigger the CI re-run automatically.\n\n### 6. Report the result\n\nAfter pushing, the agent should report the result to the orchestrator:\n\n- If CI passes on the next run, the orchestrator will merge the PR.\n- If CI still fails after the fix, the agent should retry (up to 3 attempts).\n- If all 3 attempts fail, the orchestrator will leave the PR open and label it\n  `self-update: needs-review` for a human.\n\n### 7. Exit codes\n\n- Exit 0: The fix was successfully pushed and CI was re-triggered.\n- Exit 1: The fix could not be applied, or the guardrails were violated.\n\n## Files the agent must NOT modify\n\n- `.github\u002Fworkflows\u002F` — never edit these files. If the fix requires changing CI\n  configuration, stop and report to human.\n- `scripts\u002Fself-update-fix.sh` — do not modify this script.\n\n## Reporting\n\nAfter performing the fix, the agent should output a summary including:\n\n- PR number\n- Dependency name and version\n- Failed check name\n- Files edited\n- Fix applied\n- Next steps (re-run CI, or leave open for human if 3 attempts exhausted)\n\nThe agent should output this summary to stdout so it can be captured by\n`scripts\u002Fself-update-fix.sh`.\n\n---\n\n## Skill authoring notes\n\nWhen authoring this skill for the first time, the agent should:\n\n1. Start with the guardrails (D2): never touch `.github\u002Fworkflows\u002F`.\n2. Focus on the most common fix cases: version bumps and config adjustments.\n3. Document the invocation pattern clearly so the orchestrator (`scripts\u002Fself-update-fix.sh`) can call it.\n4. Include exit codes and a summary output format so the orchestrator can\n   determine the next step (retry, label PR for human, etc.).\n\nThe skill should be authored with the goal of being as autonomous as possible\nwhile respecting the guardrails. The goal is to reduce the need for human\nintervention, but human review is the fallback when 3 fix attempts fail.\n","# Fix a dependency update PR\n\nThis skill fixes a self-update PR whose CI has failed. The agent should not\nattempt to fix the PR if it involves touching `.github\u002Fworkflows\u002F`, as that is\noutside the scope of this skill and the D2 guardrail.\n\n## When to use this skill\n\nInvoke when a self-update PR (opened by the `self-update.yml` orchestrator) has\na failing CI check and the agent is expected to fix it. The skill is called\nfrom `scripts\u002Fself-update-fix.sh` with the PR number, the dependency name and\nversion, and the failed CI check name.\n\n## How to invoke this skill\n\nThe skill is invoked from `scripts\u002Fself-update-fix.sh` with four arguments:\n\n```\nscripts\u002Fself-update-fix.sh \u003CPR_NUMBER> \u003CDEP> \u003CVERSION> \u003CFAILED_CHECK>\n```\n\nThe agent should use the Hermes CLI or Pi CLI to interact with the PR and the\ndependency versions. Which CLI to use depends on the environment setup.\n\n### Example invocation (Hermes)\n\n```\nhermes fix-pr \u003CPR_NUMBER> --dep \u003CDEP> --version \u003CVERSION> --check \u003CFAILED_CHECK>\n```\n\n### Example invocation (Pi)\n\n```\npi -p fix-pr \u003CPR_NUMBER> --dep \u003CDEP> --version \u003CVERSION> --check \u003CFAILED_CHECK>\n```\n\n> The exact CLI command depends on the environment setup. The agent should use\n> the CLI that has access to the PR and dependency versions. If neither CLI is\n> available, the agent should report the failure and exit non-zero.\n\n## What the agent should do\n\nWhen invoked, the agent should perform the following steps:\n\n### 1. Checkout the PR branch\n\n> **Guardrail**: The agent must only checkout the PR branch. Do not check out\n> `main` or any other branch.\n\nThe PR branch can be checked out via the GitHub API or `git` commands. The\nagent should use the PR number to construct the branch name (typically\n`pr-${PR_NUMBER}` or similar).\n\n### 2. Read the CI failure\n\n> **Guardrail**: The agent must only read the CI failure output. Do not modify\n> CI configuration files.\n\nThe agent should:\n- Read the CI failure output from the PR's CI run\n- Understand which check failed and why\n- Note the failed dependency version and the error message\n\n### 3. Determine the fix\n\n> **Guardrail**: The agent must not modify `.github\u002Fworkflows\u002F` files. If the fix\n> requires changing CI configuration, stop and report to human.\n\nThe agent should determine what fix is needed based on the CI failure:\n\n- **Version bump issue**: If the bump was to a version that's incompatible, the\n  agent should revert to the previous version or adjust the version range.\n- **Config issue**: If the bump requires config changes (e.g., `.node-version`),\n  the agent should adjust the config file accordingly.\n- **Dependency issue**: If a dependency version is incompatible with others,\n  the agent should adjust the version range or pin the dependency.\n\n### 4. Apply the fix\n\nThe agent should edit the relevant files to fix the issue. The following files\nmay be edited:\n\n- `etc\u002Fdeps.yaml` — update the version field\n- `etc\u002Fversions.env` — update the version field (generated from deps.yaml)\n- `.node-version` — update the Node version\n- Other project files as needed (NOT `.github\u002Fworkflows\u002F`)\n\n### 5. Push the fix\n\nThe agent should push the fix to the PR branch:\n\n```\ngit checkout \u003CPR_BRANCH>\ngit add \u003Cedited_files>\ngit commit -m \"fix: \u003Cshort description of the fix>\"\ngit push origin \u003CPR_BRANCH>\n```\n\nThis will trigger the CI re-run automatically.\n\n### 6. Report the result\n\nAfter pushing, the agent should report the result to the orchestrator:\n\n- If CI passes on the next run, the orchestrator will merge the PR.\n- If CI still fails after the fix, the agent should retry (up to 3 attempts).\n- If all 3 attempts fail, the orchestrator will leave the PR open and label it\n  `self-update: needs-review` for a human.\n\n### 7. Exit codes\n\n- Exit 0: The fix was successfully pushed and CI was re-triggered.\n- Exit 1: The fix could not be applied, or the guardrails were violated.\n\n## Files the agent must NOT modify\n\n- `.github\u002Fworkflows\u002F` — never edit these files. If the fix requires changing CI\n  configuration, stop and report to human.\n- `scripts\u002Fself-update-fix.sh` — do not modify this script.\n\n## Reporting\n\nAfter performing the fix, the agent should output a summary including:\n\n- PR number\n- Dependency name and version\n- Failed check name\n- Files edited\n- Fix applied\n- Next steps (re-run CI, or leave open for human if 3 attempts exhausted)\n\nThe agent should output this summary to stdout so it can be captured by\n`scripts\u002Fself-update-fix.sh`.\n\n---\n\n## Skill authoring notes\n\nWhen authoring this skill for the first time, the agent should:\n\n1. Start with the guardrails (D2): never touch `.github\u002Fworkflows\u002F`.\n2. Focus on the most common fix cases: version bumps and config adjustments.\n3. Document the invocation pattern clearly so the orchestrator (`scripts\u002Fself-update-fix.sh`) can call it.\n4. Include exit codes and a summary output format so the orchestrator can\n   determine the next step (retry, label PR for human, etc.).\n\nThe skill should be authored with the goal of being as autonomous as possible\nwhile respecting the guardrails. The goal is to reduce the need for human\nintervention, but human review is the fallback when 3 fix attempts fail.\n",{"name":5,"description":7,"disable-model-invocation":23},true,"main","e95aec76487a22bbbc23b63234724bc7178d4692","skills\u002Fself-update-fix","https:\u002F\u002Fgithub.com\u002Fgitricko\u002F.minions","https:\u002F\u002Fgithub.com\u002Fgitricko","2026-11-13 16:00:00",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":23},[32,35,38],{"tool":33,"command":34},"npx","npx skills add gitricko\u002F.minions --skill self-update-fix",{"tool":36,"command":37},"bunx","bunx skills add gitricko\u002F.minions --skill self-update-fix",{"tool":39,"command":40},"pnpm","pnpm dlx skills add gitricko\u002F.minions --skill self-update-fix","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgitricko\u002F.minions\u002Fblob\u002Fmain\u002Fskills\u002Fself-update-fix\u002FSKILL.md",[43],{"path":44,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":47,"sourceHtmlUrl":48},"README.md","REFERENCE","参考文档",1178,"https:\u002F\u002Fgithub.com\u002Fgitricko\u002F.minions\u002Fblob\u002Fmain\u002Fskills\u002Fself-update-fix\u002FREADME.md",[50,57,64,71,78,85],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":18},"01M7B0VJ3Q0YMCTJY69FEJ4100","version-single-source","Use when adding a new component dependency or versioning a binary in install\u002Fboot scripts.","https:\u002F\u002Fgithub.com\u002Fgitricko\u002F.minions\u002Fblob\u002Fmain\u002Fskills\u002Fversion-single-source\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":18},"01M7B0V888DV8J3JY5W9Z6WCF3","tdd","Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions \"red-green-refactor\", or wants integration tests.","https:\u002F\u002Fgithub.com\u002Fgitricko\u002F.minions\u002Fblob\u002Fmain\u002Fskills\u002Ftdd\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":18},"01M7B0TVFM38JH3PBA2K219Z2X","shell-path-login","Use when a binary or script works in one shell context but not another (interactive vs non-interactive login vs non-login shell).","https:\u002F\u002Fgithub.com\u002Fgitricko\u002F.minions\u002Fblob\u002Fmain\u002Fskills\u002Fshell-path-login\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":18},"01M7B0TB57WEW0E6E9874K3C72","pr-change-log","Use when a multi-commit PR needs its description written\u002Fupdated, or when closing out a long branch with many fix commits.","https:\u002F\u002Fgithub.com\u002Fgitricko\u002F.minions\u002Fblob\u002Fmain\u002Fskills\u002Fpr-change-log\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":18},"01M7B0T2FGSV0ZFRZ46PG4BBY2","persistent-knowledge","Persistent skills\u002Fknowledge in Codespace via symlinks.","https:\u002F\u002Fgithub.com\u002Fgitricko\u002F.minions\u002Fblob\u002Fmain\u002Fskills\u002Fpersistent-knowledge\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":18},"01M7B0SSS6R0QN67MZNTEM3GWC","mnemon-seed-persistence","Persist Mnemon memory across Codespace rebuilds.","https:\u002F\u002Fgithub.com\u002Fgitricko\u002F.minions\u002Fblob\u002Fmain\u002Fskills\u002Fmnemon-seed-persistence\u002FSKILL.md",[],[]]