[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75CJKT64H9AD98PZXGE0V3A":3,"skill-same:01M75CJKT64H9AD98PZXGE0V3A":46},{"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":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M75CJKT64H9AD98PZXGE0V3A","contributing",null,"End-to-end PR workflow for opencode-swarm. Covers branch setup, conventional commits, mandatory release notes, 5-tier CI checks, and PR submission format. Load this skill before creating branches, commits, or pull requests.","agisota\u002Fold-one","agisota","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F121413592?v=4","01M75B4BRNT67EC1NDRT8QZEP2","01M75B4BS7QR9VP580MSCPTS3X",3,"MIT","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fcontributing\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: contributing\ndescription: >\n  End-to-end PR workflow for opencode-swarm. Covers branch setup, conventional\n  commits, mandatory release notes, 5-tier CI checks, and PR submission format.\n  Load this skill before creating branches, commits, or pull requests.\n---\n\n# Contributing to opencode-swarm\n\n## 1. Branch Setup\n\n```bash\ngit checkout main && git pull origin main\ngit checkout -b \u003Ctype>\u002F\u003Cshort-description>\nbun install --frozen-lockfile\n```\n\nBranch naming: `\u003Ctype>\u002F\u003Cshort-description>` (e.g. `feat\u002Fadd-retry-backoff`, `fix\u002Fplan-sync-race`).\n\n## 2. Commit Message Format (Conventional Commits)\n\nEvery commit MUST follow: `\u003Ctype>(\u003Coptional scope>): \u003Cdescription>`\n\nRules:\n- Description lowercase, no trailing period\n- Scope optional but encouraged\n\n| Type | Changelog section | Version bump |\n|------|-------------------|-------------|\n| `feat` | Features | minor |\n| `fix` | Bug Fixes | patch |\n| `perf` | Performance | patch |\n| `revert` | Reverts | patch |\n| `docs` | Documentation | none |\n| `chore` | — | none |\n| `refactor` | — | none |\n| `test` | — | none |\n| `ci` | — | none |\n| `build` | — | none |\n\nBreaking changes: add `BREAKING CHANGE: \u003Cdescription>` footer or `!` suffix on type (e.g. `feat!:`). Triggers major bump.\n\nValid examples:\n- `feat(architect): add retry backoff to SME delegation`\n- `fix(circuit-breaker): prevent race condition on concurrent invocations`\n- `refactor(swarm): extract phase orchestration into dedicated module`\n\nInvalid (rejected by CI):\n- `WIP`, `fix stuff`, `Update README`, `feat: Add feature.` (trailing period), `Feat:` (uppercase)\n\n## 3. Release Notes (MANDATORY — every PR, no exceptions)\n\n1. Read current version: `cat .release-please-manifest.json`\n2. Compute next version based on commit types (feat = minor, fix\u002Fperf = patch)\n3. Create file: `docs\u002Freleases\u002Fv{NEXT_VERSION}.md`\n\nInclude:\n- What changed (grouped by theme)\n- Why (bug report, feature request, hardening)\n- Migration steps (if any)\n- Breaking changes (if any)\n- Known caveats\n\nEven one-line changes need release notes explaining why it matters.\n\n## 4. Run All Checks Locally (5 tiers, all must pass)\n\n```bash\n# Tier 1: Quality\nbun run typecheck\nbunx biome ci .\n\n# Tier 2: Unit tests\nbun test tests\u002Funit --timeout 120000\n\n# Tier 3: Integration tests\nbun test tests\u002Fintegration .\u002Ftest --timeout 120000\n\n# Tier 4: Security & adversarial\nbun test tests\u002Fsecurity --timeout 120000\nbun test tests\u002Fadversarial --timeout 120000\n\n# Tier 5: Build + smoke\nbun run build\nbun test tests\u002Fsmoke --timeout 120000\n```\n\nIf a pre-existing unrelated failure exists, note it in the PR description but do NOT skip other tiers.\n\n## 5. Push and Open PR\n\n```bash\ngit push -u origin \u003Cbranch-name>\n```\n\nPR title MUST be a valid conventional commit: `\u003Ctype>(\u003Cscope>): \u003Cdescription>`\n\nPR body template:\n```\n## Summary\n- Bullet 1\n- Bullet 2\n\n## Test plan\n- [ ] Tier 1 quality checks pass\n- [ ] Unit tests pass\n- [ ] Integration tests pass\n- [ ] Security\u002Fadversarial tests pass\n- [ ] Build + smoke tests pass\n```\n\n## 6. Do NOT Manually Edit These Files\n\nrelease-please manages these automatically:\n- `package.json` version field\n- `CHANGELOG.md`\n- `.release-please-manifest.json`\n\nNever replace the release PR body, create tags\u002Freleases manually, or edit these files.\n\n## 7. CI Checks (all must be green)\n\n| Check | Validates |\n|-------|-----------|\n| `quality` | TypeScript compiles, Biome lint + format clean |\n| `unit` (Ubuntu, macOS, Windows) | Unit tests pass cross-platform |\n| `integration` (Ubuntu) | Integration tests pass |\n| `security` (Ubuntu) | Security & adversarial tests pass |\n| `smoke` (Ubuntu, macOS, Windows) | Package builds & smoke tests pass |\n| `pr-standards` | PR title is valid conventional commit |\n| `check-duplicates` | PR title not duplicate of open PR |\n\n## 8. GitHub Actions SHA Pinning\n\nAll `uses:` in `.github\u002Fworkflows\u002F` must be pinned to full 40-char SHA with version comment:\n```yaml\n- uses: actions\u002Fcheckout@34e114876b0b11c390a56381ad16ebd13914f8d5 # v4\n```\n\nFind SHA: `gh api repos\u002F{owner}\u002F{repo}\u002Fgit\u002Fref\u002Ftags\u002F{tag} --jq '.object.sha'`\n\n## PR Checklist\n\n- [ ] Branch created from latest `main`\n- [ ] Every commit follows `\u003Ctype>(\u003Cscope>): \u003Cdescription>`\n- [ ] PR title follows same format\n- [ ] No manual edits to `package.json` version, `CHANGELOG.md`, or `.release-please-manifest.json`\n- [ ] `docs\u002Freleases\u002Fv{NEXT_VERSION}.md` exists with release notes\n- [ ] New tests in correct `tests\u002F` subdirectory\n- [ ] Tests updated for any changed behavior\n- [ ] If modifying workflows, all `uses:` are SHA-pinned\n- [ ] All 5 CI tiers pass locally\n- [ ] PR description includes summary and test plan\n","# Contributing to opencode-swarm\n\n## 1. Branch Setup\n\n```bash\ngit checkout main && git pull origin main\ngit checkout -b \u003Ctype>\u002F\u003Cshort-description>\nbun install --frozen-lockfile\n```\n\nBranch naming: `\u003Ctype>\u002F\u003Cshort-description>` (e.g. `feat\u002Fadd-retry-backoff`, `fix\u002Fplan-sync-race`).\n\n## 2. Commit Message Format (Conventional Commits)\n\nEvery commit MUST follow: `\u003Ctype>(\u003Coptional scope>): \u003Cdescription>`\n\nRules:\n- Description lowercase, no trailing period\n- Scope optional but encouraged\n\n| Type | Changelog section | Version bump |\n|------|-------------------|-------------|\n| `feat` | Features | minor |\n| `fix` | Bug Fixes | patch |\n| `perf` | Performance | patch |\n| `revert` | Reverts | patch |\n| `docs` | Documentation | none |\n| `chore` | — | none |\n| `refactor` | — | none |\n| `test` | — | none |\n| `ci` | — | none |\n| `build` | — | none |\n\nBreaking changes: add `BREAKING CHANGE: \u003Cdescription>` footer or `!` suffix on type (e.g. `feat!:`). Triggers major bump.\n\nValid examples:\n- `feat(architect): add retry backoff to SME delegation`\n- `fix(circuit-breaker): prevent race condition on concurrent invocations`\n- `refactor(swarm): extract phase orchestration into dedicated module`\n\nInvalid (rejected by CI):\n- `WIP`, `fix stuff`, `Update README`, `feat: Add feature.` (trailing period), `Feat:` (uppercase)\n\n## 3. Release Notes (MANDATORY — every PR, no exceptions)\n\n1. Read current version: `cat .release-please-manifest.json`\n2. Compute next version based on commit types (feat = minor, fix\u002Fperf = patch)\n3. Create file: `docs\u002Freleases\u002Fv{NEXT_VERSION}.md`\n\nInclude:\n- What changed (grouped by theme)\n- Why (bug report, feature request, hardening)\n- Migration steps (if any)\n- Breaking changes (if any)\n- Known caveats\n\nEven one-line changes need release notes explaining why it matters.\n\n## 4. Run All Checks Locally (5 tiers, all must pass)\n\n```bash\n# Tier 1: Quality\nbun run typecheck\nbunx biome ci .\n\n# Tier 2: Unit tests\nbun test tests\u002Funit --timeout 120000\n\n# Tier 3: Integration tests\nbun test tests\u002Fintegration .\u002Ftest --timeout 120000\n\n# Tier 4: Security & adversarial\nbun test tests\u002Fsecurity --timeout 120000\nbun test tests\u002Fadversarial --timeout 120000\n\n# Tier 5: Build + smoke\nbun run build\nbun test tests\u002Fsmoke --timeout 120000\n```\n\nIf a pre-existing unrelated failure exists, note it in the PR description but do NOT skip other tiers.\n\n## 5. Push and Open PR\n\n```bash\ngit push -u origin \u003Cbranch-name>\n```\n\nPR title MUST be a valid conventional commit: `\u003Ctype>(\u003Cscope>): \u003Cdescription>`\n\nPR body template:\n```\n## Summary\n- Bullet 1\n- Bullet 2\n\n## Test plan\n- [ ] Tier 1 quality checks pass\n- [ ] Unit tests pass\n- [ ] Integration tests pass\n- [ ] Security\u002Fadversarial tests pass\n- [ ] Build + smoke tests pass\n```\n\n## 6. Do NOT Manually Edit These Files\n\nrelease-please manages these automatically:\n- `package.json` version field\n- `CHANGELOG.md`\n- `.release-please-manifest.json`\n\nNever replace the release PR body, create tags\u002Freleases manually, or edit these files.\n\n## 7. CI Checks (all must be green)\n\n| Check | Validates |\n|-------|-----------|\n| `quality` | TypeScript compiles, Biome lint + format clean |\n| `unit` (Ubuntu, macOS, Windows) | Unit tests pass cross-platform |\n| `integration` (Ubuntu) | Integration tests pass |\n| `security` (Ubuntu) | Security & adversarial tests pass |\n| `smoke` (Ubuntu, macOS, Windows) | Package builds & smoke tests pass |\n| `pr-standards` | PR title is valid conventional commit |\n| `check-duplicates` | PR title not duplicate of open PR |\n\n## 8. GitHub Actions SHA Pinning\n\nAll `uses:` in `.github\u002Fworkflows\u002F` must be pinned to full 40-char SHA with version comment:\n```yaml\n- uses: actions\u002Fcheckout@34e114876b0b11c390a56381ad16ebd13914f8d5 # v4\n```\n\nFind SHA: `gh api repos\u002F{owner}\u002F{repo}\u002Fgit\u002Fref\u002Ftags\u002F{tag} --jq '.object.sha'`\n\n## PR Checklist\n\n- [ ] Branch created from latest `main`\n- [ ] Every commit follows `\u003Ctype>(\u003Cscope>): \u003Cdescription>`\n- [ ] PR title follows same format\n- [ ] No manual edits to `package.json` version, `CHANGELOG.md`, or `.release-please-manifest.json`\n- [ ] `docs\u002Freleases\u002Fv{NEXT_VERSION}.md` exists with release notes\n- [ ] New tests in correct `tests\u002F` subdirectory\n- [ ] Tests updated for any changed behavior\n- [ ] If modifying workflows, all `uses:` are SHA-pinned\n- [ ] All 5 CI tiers pass locally\n- [ ] PR description includes summary and test plan\n",{"name":5,"description":7},"main","f37de8f681f0c0ca0e0ebab6e5fddf764ca7553d","skills\u002Fcontributing",1,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one","https:\u002F\u002Fagisota.github.io\u002Fold-one\u002F","https:\u002F\u002Fgithub.com\u002Fagisota","pzd.world","2026-07-04 22:32:06",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add agisota\u002Fold-one --skill contributing",{"tool":38,"command":39},"bunx","bunx skills add agisota\u002Fold-one --skill contributing",{"tool":41,"command":42},"pnpm","pnpm dlx skills add agisota\u002Fold-one --skill contributing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fcontributing\u002FSKILL.md",true,[],[47,54,61,70,77,84],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":18},"01M75KRGZWQWE9JDBS6RX42NWV","zoom-out","Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-out\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M75KRCZHKE0ZYAQFFYHS0YNP","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":65,"licenseFileUrl":66,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":18},"01M75KR94KYQ30DTE1P9WNDAE0","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":18},"01M75KR3H13YJ9QHMD49818FA1","yara-rule-authoring","Guides authoring of high-quality YARA-X detection rules for malware identification. Use when writing, reviewing, or optimizing YARA rules. Covers naming conventions, string selection, performance optimization, migration from legacy YARA, and false positive reduction. Triggers on: YARA, YARA-X, malware detection, threat hunting, IOC, signature, crx module, dex module.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyara-rule-authoring\u002FSKILL.md",[],[],{"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":18},"01M75KQMPY8A4Y8XTDD2DT0M9T","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-twitter-growth\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":18},"01M75KQHNZ0ANZNJGZY6M8MDAK","x-api","X\u002FTwitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-api\u002FSKILL.md",[],[]]