[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ADKRM2GD5PF39SBPZN2C17":3,"skill-same:01M6ADKRM2GD5PF39SBPZN2C17":75},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":23,"linkOnly":24,"markdownContent":25,"markdownBody":26,"frontMatter":27,"refName":32,"commitSha":33,"skillDirectory":34,"forksCount":35,"repositoryHtmlUrl":36,"repositoryHomepageUrl":37,"ownerHtmlUrl":38,"ownerBlogUrl":39,"ownerDescription":40,"updatedAt":41,"install":42,"resources":54},"01M6ADKRM2GD5PF39SBPZN2C17","fix-issue",null,"Fix a GitHub issue by number. Reads the issue, implements a fix, and prepares a commit.","davila7\u002Fclaude-with-skills","davila7","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6216945?v=4","01M6ADEWWFPS191NFM0Y1EX1JH","Daniel Avila","01M6ADJHY7XW1NT6J5EJ61Q42B",13,"MIT","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-with-skills\u002Fblob\u002Fmain\u002Fsrc\u002Fcontent\u002Fdocs\u002F02-intermediate\u002Flesson-04-arguments\u002Fexamples\u002Ffix-issue\u002FSKILL.md",[],[19,20,21,22],"fix issue","github","commit","gh issue","2026-11-10 10:12:30",false,"---\ntitle: \"fix-issue\"\nname: fix-issue\ndescription: Fix a GitHub issue by number. Reads the issue, implements a fix, and prepares a commit.\ndisable-model-invocation: true\nargument-hint: [issue-number]\nallowed-tools: Bash(gh issue view *) Bash(gh issue list *) Read Grep Glob\n---\n\n## Fix GitHub issue\n\n### Step 1: Read the issue\n\nRun:\n```\ngh issue view $ARGUMENTS\n```\n\nIf the issue does not exist or the `gh` CLI is not authenticated, stop and report the error. Do not proceed.\n\n### Step 2: Understand the requirements\n\nFrom the issue output, identify:\n- The reported problem or requested feature\n- Any reproduction steps or acceptance criteria mentioned in the issue body\n- Labels that indicate the type of work (bug, enhancement, documentation, etc.)\n- Any linked issues or pull requests that provide additional context\n\nIf the issue is unclear or underspecified, state the assumptions you are making before proceeding.\n\n### Step 3: Find the relevant code\n\nSearch for code related to the issue:\n- Use `grep -r` to find files referencing the relevant function, component, or error message\n- Read the most relevant files to understand the current implementation\n- Identify where the change should be made and why\n\n### Step 4: Implement a minimal fix\n\nMake the smallest change that correctly addresses the issue. Follow the existing code patterns in the affected file:\n- Match the style, naming conventions, and error handling patterns already in use\n- Do not refactor unrelated code\n- Do not add features beyond what the issue describes\n\n### Step 5: Write or update tests\n\nIf the codebase has tests:\n- Add a test that fails before the fix and passes after\n- Update any existing tests that are affected by the change\n- Run the existing tests to confirm nothing is broken (use the test runner you find in `package.json` or the nearest test configuration file)\n\nIf you cannot determine the test runner, note that and ask the user.\n\n### Step 6: Prepare a commit message\n\nStage the changes and write a commit message in this format:\n\n```\nfix: \u003Cshort description matching the issue title>\n\nFixes #$ARGUMENTS\n```\n\nDo not commit automatically. Present the staged diff and the proposed commit message, then wait for the user to confirm or adjust before committing.\n","## Fix GitHub issue\n\n### Step 1: Read the issue\n\nRun:\n```\ngh issue view $ARGUMENTS\n```\n\nIf the issue does not exist or the `gh` CLI is not authenticated, stop and report the error. Do not proceed.\n\n### Step 2: Understand the requirements\n\nFrom the issue output, identify:\n- The reported problem or requested feature\n- Any reproduction steps or acceptance criteria mentioned in the issue body\n- Labels that indicate the type of work (bug, enhancement, documentation, etc.)\n- Any linked issues or pull requests that provide additional context\n\nIf the issue is unclear or underspecified, state the assumptions you are making before proceeding.\n\n### Step 3: Find the relevant code\n\nSearch for code related to the issue:\n- Use `grep -r` to find files referencing the relevant function, component, or error message\n- Read the most relevant files to understand the current implementation\n- Identify where the change should be made and why\n\n### Step 4: Implement a minimal fix\n\nMake the smallest change that correctly addresses the issue. Follow the existing code patterns in the affected file:\n- Match the style, naming conventions, and error handling patterns already in use\n- Do not refactor unrelated code\n- Do not add features beyond what the issue describes\n\n### Step 5: Write or update tests\n\nIf the codebase has tests:\n- Add a test that fails before the fix and passes after\n- Update any existing tests that are affected by the change\n- Run the existing tests to confirm nothing is broken (use the test runner you find in `package.json` or the nearest test configuration file)\n\nIf you cannot determine the test runner, note that and ask the user.\n\n### Step 6: Prepare a commit message\n\nStage the changes and write a commit message in this format:\n\n```\nfix: \u003Cshort description matching the issue title>\n\nFixes #$ARGUMENTS\n```\n\nDo not commit automatically. Present the staged diff and the proposed commit message, then wait for the user to confirm or adjust before committing.\n",{"name":5,"title":5,"description":7,"allowed-tools":28,"argument-hint":29,"disable-model-invocation":31},"Bash(gh issue view *) Bash(gh issue list *) Read Grep Glob",[30],"issue-number",true,"main","55e6468ba43345d07c8a68de983e58403db57c25","src\u002Fcontent\u002Fdocs\u002F02-intermediate\u002Flesson-04-arguments\u002Fexamples\u002Ffix-issue",1,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-with-skills","https:\u002F\u002Fclaude-with-skills.vercel.app","https:\u002F\u002Fgithub.com\u002Fdavila7","https:\u002F\u002Fdanielavila.me","Building AI dev tools with LLMs","2026-05-15 21:54:25",{"source":8,"skillName":5,"commands":43,"prompt":53,"zipAvailable":31},[44,47,50],{"tool":45,"command":46},"npx","npx skills add davila7\u002Fclaude-with-skills --skill fix-issue",{"tool":48,"command":49},"bunx","bunx skills add davila7\u002Fclaude-with-skills --skill fix-issue",{"tool":51,"command":52},"pnpm","pnpm dlx skills add davila7\u002Fclaude-with-skills --skill fix-issue","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-with-skills\u002Fblob\u002Fmain\u002Fsrc\u002Fcontent\u002Fdocs\u002F02-intermediate\u002Flesson-04-arguments\u002Fexamples\u002Ffix-issue\u002FSKILL.md",[55,61,67,71],{"path":56,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":60},"_lib\u002Fbrowse-client.ts","SCRIPT","脚本",11521,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fgstack\u002Fbrowser-skills\u002Fhackernews-frontpage\u002F_lib\u002Fbrowse-client.ts",{"path":62,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":65,"sourceHtmlUrl":66},"fixtures\u002Fhn-2026-04-26.html","REFERENCE","参考文档",5162,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fgstack\u002Fbrowser-skills\u002Fhackernews-frontpage\u002Ffixtures\u002Fhn-2026-04-26.html",{"path":68,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":69,"sourceHtmlUrl":70},"script.test.ts",3865,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fgstack\u002Fbrowser-skills\u002Fhackernews-frontpage\u002Fscript.test.ts",{"path":72,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":73,"sourceHtmlUrl":74},"script.ts",4679,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fgstack\u002Fbrowser-skills\u002Fhackernews-frontpage\u002Fscript.ts",[76,92,102,108,116,126],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":23},"01M6ADNEC991ZW0GD2D4MY6NEP","tag-version","Bump the package version and create an annotated git tag. Accepts a semantic version number (1.2.0) or a bump type (patch, minor, major). Does not push — use the publish skill to push. Use as part of a release workflow.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-with-skills\u002Fblob\u002Fmain\u002Fsrc\u002Fcontent\u002Fdocs\u002F03-advanced\u002Flesson-08-plugins-and-distribution\u002Fexamples\u002Frelease-plugin\u002Fskills\u002Ftag-version\u002FSKILL.md",[],[83,84,85,86,87,88,89,90,91],"tag version","workflow","create","release","git","push","npm","package","publish",{"skillNo":93,"name":86,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":23},"01M6ADNCNHCXNHVAW43ZV43ZC8","Run the complete release workflow: changelog entry, version bump, git tag, and GitHub release. Invokes changelog-entry, tag-version, and publish in sequence. Use when releasing a new version of the project.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-with-skills\u002Fblob\u002Fmain\u002Fsrc\u002Fcontent\u002Fdocs\u002F03-advanced\u002Flesson-08-plugins-and-distribution\u002Fexamples\u002Frelease-plugin\u002Fskills\u002Frelease\u002FSKILL.md",[],[86,87,98,89,99,100,91,101,20,84],"changelog","changelog entry","run","status",{"skillNo":103,"name":91,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":23},"01M6ADNAWDDDDX4CS69E1D496X","Push the current branch and all tags to origin, then create a GitHub release using the latest tag and its CHANGELOG.md entry. Use after tag-version to complete a release.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-with-skills\u002Fblob\u002Fmain\u002Fsrc\u002Fcontent\u002Fdocs\u002F03-advanced\u002Flesson-08-plugins-and-distribution\u002Fexamples\u002Frelease-plugin\u002Fskills\u002Fpublish\u002FSKILL.md",[],[91,88,20,85,86,87,98],{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":23},"01M6ADN9MP0ASQ6SX14NEPP5XE","changelog-entry","Draft the changelog entry for all unreleased commits in Keep a Changelog format. Groups commits into Added, Changed, Fixed, Removed, and Security. Use before releasing a new version or when updating CHANGELOG.md.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-with-skills\u002Fblob\u002Fmain\u002Fsrc\u002Fcontent\u002Fdocs\u002F03-advanced\u002Flesson-08-plugins-and-distribution\u002Fexamples\u002Frelease-plugin\u002Fskills\u002Fchangelog-entry\u002FSKILL.md",[],[99,98,115,87],"security",{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":23},"01M6ADN8243TD9X8FH7FCQ608R","auto-format-on-edit","Automatically format code files after every edit using Prettier and ESLint. Active in the background whenever Claude edits a file. Formatting is silent — no prompts, no output unless a formatter fails. Use when you want consistent formatting enforced automatically during a coding session.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-with-skills\u002Fblob\u002Fmain\u002Fsrc\u002Fcontent\u002Fdocs\u002F03-advanced\u002Flesson-07-hooks-in-skills\u002Fexamples\u002Fauto-format-on-edit\u002FSKILL.md",[],[123,124,125],"auto format on edit","code","file",{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":137,"publishedAt":23},"01M6ADN5VVNV7Y2WPYQA13M4ZQ","code-quality-audit","Run a comprehensive code quality audit covering security, performance, and maintainability. Use for quarterly audits, pre-release reviews, or when onboarding to a large codebase.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-with-skills\u002Fblob\u002Fmain\u002Fsrc\u002Fcontent\u002Fdocs\u002F03-advanced\u002Flesson-06-context-window-mastery\u002Fexamples\u002Flightweight-orchestrator\u002FSKILL.md",[132],{"categoryNo":133,"categoryName":134,"taxonomyType":135,"taxonomyTypeDesc":136},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[138,139,124,140,141,100,86,142,115],"code quality audit","audit","code quality","performance","onboarding"]