[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75CMCTERN579RQX1JBAHPVB":3,"skill-same:01M75CMCTERN579RQX1JBAHPVB":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},"01M75CMCTERN579RQX1JBAHPVB","create-pull-request",null,"Create a GitHub pull request following project conventions. Use when the user asks to create a PR, submit changes for review, or open a pull request. Handles commit analysis, branch management, and PR creation using the gh CLI tool.","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\u002Fcreate-pull-request\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: create-pull-request\ndescription: Create a GitHub pull request following project conventions. Use when the user asks to create a PR, submit changes for review, or open a pull request. Handles commit analysis, branch management, and PR creation using the gh CLI tool.\nlicense: MIT\n---\n\n# Create Pull Request\n\nThis skill guides you through creating a well-structured GitHub pull request that follows project conventions and best practices.\n\n## Prerequisites Check\n\nBefore proceeding, verify the following:\n\n### 1. Check if `gh` CLI is installed\n\n```bash\ngh --version\n```\n\nIf not installed, inform the user:\n> The GitHub CLI (`gh`) is required but not installed. Please install it:\n> - macOS: `brew install gh`\n> - Other: https:\u002F\u002Fcli.github.com\u002F\n\n### 2. Check if authenticated with GitHub\n\n```bash\ngh auth status\n```\n\nIf not authenticated, guide the user to run `gh auth login`.\n\n### 3. Check for related skills\n\nBefore creating a PR, check if any skills are available that relate to code review, CI, or testing. These should be invoked first as prerequisites.\n\nLook for skills with descriptions containing:\n- \"review\" (e.g., code review, PR review, web-design-guidelines)\n- \"CI\" or \"ci-fix\" (e.g., fixing CI failures)\n- \"testing\" or \"test\" (e.g., running tests, webapp-testing)\n\nIf such skills exist, invoke them before proceeding with PR creation. For example:\n- If a `ci-fix` skill exists and CI is failing, use it to diagnose and fix issues\n- If a `web-design-guidelines` skill exists for UI changes, use it to review the changes\n- If a testing skill exists, use it to ensure tests pass\n\n**Only proceed with PR creation after these prerequisite skills have been satisfied.**\n\n### 4. Verify clean working directory\n\n```bash\ngit status\n```\n\nIf there are uncommitted changes, ask the user whether to:\n- Commit them as part of this PR\n- Stash them temporarily\n- Discard them (with caution)\n\n## Check for Existing PR\n\nBefore gathering context, check if a PR already exists for the current branch:\n\n```bash\ngh pr list --head $(git branch --show-current) --json number,title,url\n```\n\nIf a PR already exists:\n- Display the existing PR details (number, title, URL)\n- Ask the user if they want to:\n  - View the existing PR: `gh pr view`\n  - Update the existing PR (push more commits and the PR will update automatically)\n  - Close the existing PR and create a new one\n\n**Only proceed with creating a new PR if no PR exists for this branch.**\n\n## Gather Context\n\n### 1. Identify the current branch\n\n```bash\ngit branch --show-current\n```\n\nEnsure you're not on `main` or `master`. If so, ask the user to create or switch to a feature branch.\n\n### 2. Find the base branch\n\n```bash\ngit remote show origin | grep \"HEAD branch\"\n```\n\nThis is typically `main` or `master`.\n\n### 3. Analyze recent commits relevant to this PR\n\n```bash\ngit log origin\u002Fmain..HEAD --oneline --no-decorate\n```\n\nReview these commits to understand:\n- What changes are being introduced\n- The scope of the PR (single feature\u002Ffix or multiple changes)\n- Whether commits should be squashed or reorganized\n\n### 4. Review the diff\n\n```bash\ngit diff origin\u002Fmain..HEAD --stat\n```\n\nThis shows which files changed and helps identify the type of change.\n\n## Information Gathering\n\nGather the following information from available context (commit messages, branch names, changed files):\n\n### Information to Extract\n\n1. **Related Issue Number**: Look for patterns like `#123`, `fixes #123`, or `closes #123` in:\n   - Commit messages\n   - Branch name (e.g., `fix\u002Fissue-123`, `feature\u002F123-new-login`)\n   - If found, include it in the PR title and\u002For description\n   - If not found, proceed without it\n\n2. **Description**: What problem does this solve? Why were these changes made?\n   - Infer from commit messages and diff\n   - Describe the changes made\n\n3. **Type of Change**: Bug fix, new feature, breaking change, refactor, cosmetic, documentation, or workflow\n   - Determine from commit messages and changed files\n\n4. **Test Procedure**: How was this tested? What could break?\n   - Mention test files if they were modified\n   - Describe testing approach if evident from changes\n\n### Intelligent PR Title Generation\n\nThe PR title should be descriptive and meaningful. **Avoid generic titles** like:\n- \"initial commit\"\n- \"fix\"\n- \"update\"\n- \"changes\"\n\nInstead, create a title that clearly summarizes the changes. Consider these approaches:\n\n#### 1. Conventional Commits Format\n\nCheck if the project uses conventional commits by analyzing:\n- Commit messages for patterns like `feat:`, `fix:`, `docs:`, `refactor:`, `test:`, `chore:`\n- Branch name prefixes like `feat\u002F`, `fix\u002F`, `docs\u002F`\n\nIf conventional commits are detected, use the appropriate prefix for the PR title:\n- `feat: Add user authentication with OAuth`\n- `fix: Resolve memory leak in data processing`\n- `docs: Update API documentation for v2 endpoints`\n- `refactor: Simplify error handling logic`\n- `test: Add integration tests for payment flow`\n- `chore: Update dependencies to latest versions`\n\n**Include issue number if found:**\n- `feat: Add user authentication with OAuth (#123)`\n- `fix(auth): Resolve memory leak in data processing (fixes #456)`\n\n#### 2. Descriptive Summary\n\nIf not using conventional commits, create a clear, action-oriented title:\n- Good: \"Add pagination to search results\"\n- Bad: \"initial commit\"\n- Good: \"Fix race condition in authentication flow\"\n- Bad: \"fix bug\"\n\n**Include issue number if found:**\n- \"Add pagination to search results (#123)\"\n- \"Fix race condition in authentication flow (fixes #456)\"\n\n#### 3. Title Generation Strategy\n\n1. Look at the most significant commit message (often the first or last)\n2. Identify the main change from the diff (new feature, bug fix, etc.)\n3. Extract the issue title if linked\n4. If none of these provide a good title, synthesize one from the changed files and their purpose\n5. Append issue number to title if found in commits or branch name\n\n## Git Best Practices\n\nBefore creating the PR, consider these best practices:\n\n### Commit Hygiene\n\n1. **Atomic commits**: Each commit should represent a single logical change\n2. **Clear commit messages**: Follow conventional commit format when possible\n3. **No merge commits**: Prefer rebasing over merging to keep history clean\n\n### Branch Management\n\n1. **Rebase on latest main** (if needed):\n   ```bash\n   git fetch origin\n   git rebase origin\u002Fmain\n   ```\n\n2. **Squash if appropriate**: If there are many small \"WIP\" commits, consider interactive rebase:\n   ```bash\n   git rebase -i origin\u002Fmain\n   ```\n   Only suggest this if commits appear messy and the user is comfortable with rebasing.\n\n### Push Changes\n\nEnsure all commits are pushed:\n```bash\ngit push origin HEAD\n```\n\nIf the branch was rebased, you may need:\n```bash\ngit push origin HEAD --force-with-lease\n```\n\n## Create the Pull Request\n\n**IMPORTANT**: Read and use the PR template at `.github\u002Fpull_request_template.md` if it exists. The PR body format should match the template structure.\n\nWhen filling out the template:\n- Include issue number (e.g., `Fixes #123`, `Closes #456`) if found in context\n- If no template exists, create a clear description with:\n  - Summary of changes\n  - Related issue (if found)\n  - Testing performed\n  - Any breaking changes or notable impacts\n- Fill in all sections with relevant information gathered from commits and context\n- Mark the appropriate \"Type of Change\" checkbox(es) if template has them\n- Complete any checklist items that apply\n\n### Draft PR Decision\n\nDecide whether to create a draft PR or a regular PR based on the following:\n\n**Use `--draft` flag when:**\n- Changes are incomplete or work-in-progress, but you want early feedback\n- Tests are currently failing and you need help debugging\n- You're blocked on an architectural decision and need guidance\n- Creating the PR as a bookmark for work you'll continue later\n- You want to trigger CI checks but aren't ready for full review\n\n**Use regular PR (no `--draft`) when:**\n- All tests pass and code is ready for review\n- Changes are complete and you're confident in the approach\n- You want the PR to be reviewed and merged soon\n\n### Create PR with gh CLI\n\nFor a regular PR:\n```bash\ngh pr create --title \"PR_TITLE\" --body \"PR_BODY\" --base main\n```\n\nFor a draft PR:\n```bash\ngh pr create --title \"PR_TITLE\" --body \"PR_BODY\" --base main --draft\n```\n\n## Post-Creation\n\nAfter creating the PR:\n\n### 1. Open PR in browser for verification\n\nImmediately open the PR in the browser to verify it was created correctly:\n\n```bash\ngh pr view --web\n```\n\nThis allows you to:\n- Verify the PR title and description render correctly\n- Check that all links work (issue references, etc.)\n- Ensure the diff looks as expected\n- See any immediate CI status\n\n### 2. Remind about CI checks\n\nTests and linting will run automatically. Monitor the checks to ensure they pass.\n\n### 3. Suggest next steps (if needed)\n\n- Add reviewers if needed: `gh pr edit --add-reviewer USERNAME`\n- Add labels if needed: `gh pr edit --add-label \"bug\"`\n\n## Error Handling\n\n### Common Issues\n\n1. **No commits ahead of main**: The branch has no changes to submit\n   - Ask if the user meant to work on a different branch\n\n2. **Branch not pushed**: Remote doesn't have the branch\n   - Push the branch first: `git push -u origin HEAD`\n\n3. **PR already exists**: A PR for this branch already exists\n   - Show the existing PR: `gh pr view`\n   - Ask if they want to update it instead\n\n4. **Merge conflicts**: Branch conflicts with base\n   - Guide user through resolving conflicts or rebasing\n\n## Summary Checklist\n\nBefore finalizing, ensure:\n- [ ] `gh` CLI is installed and authenticated\n- [ ] Related review\u002FCI\u002Ftesting skills have been invoked\n- [ ] No existing PR exists for this branch\n- [ ] Working directory is clean\n- [ ] All commits are pushed\n- [ ] Branch is up-to-date with base branch\n- [ ] PR title is descriptive and meaningful (not generic)\n- [ ] PR title uses conventional commit format if project uses it\n- [ ] Issue number included in title\u002Fdescription if found in context\n- [ ] PR description follows template (if template exists)\n- [ ] Appropriate type of change is selected\n- [ ] Correct draft\u002Fregular status chosen\n- [ ] PR opened in browser for verification\n","# Create Pull Request\n\nThis skill guides you through creating a well-structured GitHub pull request that follows project conventions and best practices.\n\n## Prerequisites Check\n\nBefore proceeding, verify the following:\n\n### 1. Check if `gh` CLI is installed\n\n```bash\ngh --version\n```\n\nIf not installed, inform the user:\n> The GitHub CLI (`gh`) is required but not installed. Please install it:\n> - macOS: `brew install gh`\n> - Other: https:\u002F\u002Fcli.github.com\u002F\n\n### 2. Check if authenticated with GitHub\n\n```bash\ngh auth status\n```\n\nIf not authenticated, guide the user to run `gh auth login`.\n\n### 3. Check for related skills\n\nBefore creating a PR, check if any skills are available that relate to code review, CI, or testing. These should be invoked first as prerequisites.\n\nLook for skills with descriptions containing:\n- \"review\" (e.g., code review, PR review, web-design-guidelines)\n- \"CI\" or \"ci-fix\" (e.g., fixing CI failures)\n- \"testing\" or \"test\" (e.g., running tests, webapp-testing)\n\nIf such skills exist, invoke them before proceeding with PR creation. For example:\n- If a `ci-fix` skill exists and CI is failing, use it to diagnose and fix issues\n- If a `web-design-guidelines` skill exists for UI changes, use it to review the changes\n- If a testing skill exists, use it to ensure tests pass\n\n**Only proceed with PR creation after these prerequisite skills have been satisfied.**\n\n### 4. Verify clean working directory\n\n```bash\ngit status\n```\n\nIf there are uncommitted changes, ask the user whether to:\n- Commit them as part of this PR\n- Stash them temporarily\n- Discard them (with caution)\n\n## Check for Existing PR\n\nBefore gathering context, check if a PR already exists for the current branch:\n\n```bash\ngh pr list --head $(git branch --show-current) --json number,title,url\n```\n\nIf a PR already exists:\n- Display the existing PR details (number, title, URL)\n- Ask the user if they want to:\n  - View the existing PR: `gh pr view`\n  - Update the existing PR (push more commits and the PR will update automatically)\n  - Close the existing PR and create a new one\n\n**Only proceed with creating a new PR if no PR exists for this branch.**\n\n## Gather Context\n\n### 1. Identify the current branch\n\n```bash\ngit branch --show-current\n```\n\nEnsure you're not on `main` or `master`. If so, ask the user to create or switch to a feature branch.\n\n### 2. Find the base branch\n\n```bash\ngit remote show origin | grep \"HEAD branch\"\n```\n\nThis is typically `main` or `master`.\n\n### 3. Analyze recent commits relevant to this PR\n\n```bash\ngit log origin\u002Fmain..HEAD --oneline --no-decorate\n```\n\nReview these commits to understand:\n- What changes are being introduced\n- The scope of the PR (single feature\u002Ffix or multiple changes)\n- Whether commits should be squashed or reorganized\n\n### 4. Review the diff\n\n```bash\ngit diff origin\u002Fmain..HEAD --stat\n```\n\nThis shows which files changed and helps identify the type of change.\n\n## Information Gathering\n\nGather the following information from available context (commit messages, branch names, changed files):\n\n### Information to Extract\n\n1. **Related Issue Number**: Look for patterns like `#123`, `fixes #123`, or `closes #123` in:\n   - Commit messages\n   - Branch name (e.g., `fix\u002Fissue-123`, `feature\u002F123-new-login`)\n   - If found, include it in the PR title and\u002For description\n   - If not found, proceed without it\n\n2. **Description**: What problem does this solve? Why were these changes made?\n   - Infer from commit messages and diff\n   - Describe the changes made\n\n3. **Type of Change**: Bug fix, new feature, breaking change, refactor, cosmetic, documentation, or workflow\n   - Determine from commit messages and changed files\n\n4. **Test Procedure**: How was this tested? What could break?\n   - Mention test files if they were modified\n   - Describe testing approach if evident from changes\n\n### Intelligent PR Title Generation\n\nThe PR title should be descriptive and meaningful. **Avoid generic titles** like:\n- \"initial commit\"\n- \"fix\"\n- \"update\"\n- \"changes\"\n\nInstead, create a title that clearly summarizes the changes. Consider these approaches:\n\n#### 1. Conventional Commits Format\n\nCheck if the project uses conventional commits by analyzing:\n- Commit messages for patterns like `feat:`, `fix:`, `docs:`, `refactor:`, `test:`, `chore:`\n- Branch name prefixes like `feat\u002F`, `fix\u002F`, `docs\u002F`\n\nIf conventional commits are detected, use the appropriate prefix for the PR title:\n- `feat: Add user authentication with OAuth`\n- `fix: Resolve memory leak in data processing`\n- `docs: Update API documentation for v2 endpoints`\n- `refactor: Simplify error handling logic`\n- `test: Add integration tests for payment flow`\n- `chore: Update dependencies to latest versions`\n\n**Include issue number if found:**\n- `feat: Add user authentication with OAuth (#123)`\n- `fix(auth): Resolve memory leak in data processing (fixes #456)`\n\n#### 2. Descriptive Summary\n\nIf not using conventional commits, create a clear, action-oriented title:\n- Good: \"Add pagination to search results\"\n- Bad: \"initial commit\"\n- Good: \"Fix race condition in authentication flow\"\n- Bad: \"fix bug\"\n\n**Include issue number if found:**\n- \"Add pagination to search results (#123)\"\n- \"Fix race condition in authentication flow (fixes #456)\"\n\n#### 3. Title Generation Strategy\n\n1. Look at the most significant commit message (often the first or last)\n2. Identify the main change from the diff (new feature, bug fix, etc.)\n3. Extract the issue title if linked\n4. If none of these provide a good title, synthesize one from the changed files and their purpose\n5. Append issue number to title if found in commits or branch name\n\n## Git Best Practices\n\nBefore creating the PR, consider these best practices:\n\n### Commit Hygiene\n\n1. **Atomic commits**: Each commit should represent a single logical change\n2. **Clear commit messages**: Follow conventional commit format when possible\n3. **No merge commits**: Prefer rebasing over merging to keep history clean\n\n### Branch Management\n\n1. **Rebase on latest main** (if needed):\n   ```bash\n   git fetch origin\n   git rebase origin\u002Fmain\n   ```\n\n2. **Squash if appropriate**: If there are many small \"WIP\" commits, consider interactive rebase:\n   ```bash\n   git rebase -i origin\u002Fmain\n   ```\n   Only suggest this if commits appear messy and the user is comfortable with rebasing.\n\n### Push Changes\n\nEnsure all commits are pushed:\n```bash\ngit push origin HEAD\n```\n\nIf the branch was rebased, you may need:\n```bash\ngit push origin HEAD --force-with-lease\n```\n\n## Create the Pull Request\n\n**IMPORTANT**: Read and use the PR template at `.github\u002Fpull_request_template.md` if it exists. The PR body format should match the template structure.\n\nWhen filling out the template:\n- Include issue number (e.g., `Fixes #123`, `Closes #456`) if found in context\n- If no template exists, create a clear description with:\n  - Summary of changes\n  - Related issue (if found)\n  - Testing performed\n  - Any breaking changes or notable impacts\n- Fill in all sections with relevant information gathered from commits and context\n- Mark the appropriate \"Type of Change\" checkbox(es) if template has them\n- Complete any checklist items that apply\n\n### Draft PR Decision\n\nDecide whether to create a draft PR or a regular PR based on the following:\n\n**Use `--draft` flag when:**\n- Changes are incomplete or work-in-progress, but you want early feedback\n- Tests are currently failing and you need help debugging\n- You're blocked on an architectural decision and need guidance\n- Creating the PR as a bookmark for work you'll continue later\n- You want to trigger CI checks but aren't ready for full review\n\n**Use regular PR (no `--draft`) when:**\n- All tests pass and code is ready for review\n- Changes are complete and you're confident in the approach\n- You want the PR to be reviewed and merged soon\n\n### Create PR with gh CLI\n\nFor a regular PR:\n```bash\ngh pr create --title \"PR_TITLE\" --body \"PR_BODY\" --base main\n```\n\nFor a draft PR:\n```bash\ngh pr create --title \"PR_TITLE\" --body \"PR_BODY\" --base main --draft\n```\n\n## Post-Creation\n\nAfter creating the PR:\n\n### 1. Open PR in browser for verification\n\nImmediately open the PR in the browser to verify it was created correctly:\n\n```bash\ngh pr view --web\n```\n\nThis allows you to:\n- Verify the PR title and description render correctly\n- Check that all links work (issue references, etc.)\n- Ensure the diff looks as expected\n- See any immediate CI status\n\n### 2. Remind about CI checks\n\nTests and linting will run automatically. Monitor the checks to ensure they pass.\n\n### 3. Suggest next steps (if needed)\n\n- Add reviewers if needed: `gh pr edit --add-reviewer USERNAME`\n- Add labels if needed: `gh pr edit --add-label \"bug\"`\n\n## Error Handling\n\n### Common Issues\n\n1. **No commits ahead of main**: The branch has no changes to submit\n   - Ask if the user meant to work on a different branch\n\n2. **Branch not pushed**: Remote doesn't have the branch\n   - Push the branch first: `git push -u origin HEAD`\n\n3. **PR already exists**: A PR for this branch already exists\n   - Show the existing PR: `gh pr view`\n   - Ask if they want to update it instead\n\n4. **Merge conflicts**: Branch conflicts with base\n   - Guide user through resolving conflicts or rebasing\n\n## Summary Checklist\n\nBefore finalizing, ensure:\n- [ ] `gh` CLI is installed and authenticated\n- [ ] Related review\u002FCI\u002Ftesting skills have been invoked\n- [ ] No existing PR exists for this branch\n- [ ] Working directory is clean\n- [ ] All commits are pushed\n- [ ] Branch is up-to-date with base branch\n- [ ] PR title is descriptive and meaningful (not generic)\n- [ ] PR title uses conventional commit format if project uses it\n- [ ] Issue number included in title\u002Fdescription if found in context\n- [ ] PR description follows template (if template exists)\n- [ ] Appropriate type of change is selected\n- [ ] Correct draft\u002Fregular status chosen\n- [ ] PR opened in browser for verification\n",{"name":5,"license":14,"description":7},"main","f37de8f681f0c0ca0e0ebab6e5fddf764ca7553d","skills\u002Fcreate-pull-request",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 create-pull-request",{"tool":38,"command":39},"bunx","bunx skills add agisota\u002Fold-one --skill create-pull-request",{"tool":41,"command":42},"pnpm","pnpm dlx skills add agisota\u002Fold-one --skill create-pull-request","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fcreate-pull-request\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",[],[]]