[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75DCGNZ4AMXK5JJAT8ESFJ3":3,"skill-same:01M75DCGNZ4AMXK5JJAT8ESFJ3":46},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M75DCGNZ4AMXK5JJAT8ESFJ3","code-fix",null,"Ensure Go implementation changes are verified with just check, fix failures until success, and handle coverage failures by adding meaningful tests or using narrow, explicit Go coverage exclusions.","tooppoo\u002Fgit-kura","tooppoo","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F10760022?v=4","01M75DC13XZWSD4JMW8FWSQNM8","philomagi","01M75DC14FHTBED4CA8FQJFQJS",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Ftooppoo\u002Fgit-kura\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcode-fix\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: code-fix\ndescription: Ensure Go implementation changes are verified with just check, fix failures until success, and handle coverage failures by adding meaningful tests or using narrow, explicit Go coverage exclusions.\n---\n\n# go-make-check-verification\n\n## Purpose\n\nEnsure that every Go implementation change is verified by the repository's standard check command, and that coverage failures are resolved by improving tests unless there is a justified reason to exclude verification-only code from coverage.\n\n## When to use this skill\n\nUse this skill whenever you modify Go implementation code, Go tests, build configuration, schemas, fixtures, generated code configuration, or coverage-related configuration in this repository.\n\n## Required verification loop\n\nAfter changing implementation or test code, always run:\n\n```sh id=\"cr99o0\"\njust check\n```\n\nIf `just check` fails:\n\n1. Read the error message carefully.\n2. Identify the concrete failing category, such as:\n\n   * formatting failure\n   * lint failure\n   * compile failure\n   * unit test failure\n   * integration test failure\n   * schema or fixture validation failure\n   * coverage failure\n3. Fix the cause indicated by the error.\n4. Run `just check` again.\n5. Continue this loop until `just check` succeeds.\n\nDo not treat the task as complete while `just check` is still failing.\n\nIf `just check` cannot be executed because of an environment limitation, missing tool, missing permission, network restriction, or external service failure, stop and report:\n\n* the exact command attempted\n* the exact error output\n* whether the failure is caused by the repository code or by the execution environment\n* the remaining unverified risk\n\n## Go coverage policy\n\nIf coverage is low or a coverage threshold fails, first assume the correct response is to add or improve tests.\n\nPrefer tests that cover observable behavior rather than tests that merely execute lines for the sake of increasing coverage.\n\nWhen adding tests, prioritize:\n\n1. public behavior and CLI-visible behavior\n2. parser \u002F evaluator \u002F reporter boundaries\n3. error cases and validation failures\n4. regression cases related to the change being made\n5. edge cases that are likely to break silently\n6. package boundary behavior, especially when interfaces or adapters are involved\n\nDo not lower the coverage threshold merely to make the check pass.\n\n## Go coverage exclusion policy\n\nCoverage exclusion is allowed only when the uncovered code is primarily verification-only, scaffolding-only, generated, or structurally unsuitable for meaningful behavioral testing.\n\nExamples that may be eligible:\n\n* builtin module implementations used mainly as validation scaffolding\n* generated code\n* test-only adapters\n* fixture-only helpers\n* code that exists only to support schema or artifact validation\n* unreachable defensive branches that cannot be exercised without corrupting invariants\n\nBefore excluding code from coverage, confirm that adding a meaningful test would not be the better fix.\n\nWhen excluding code, keep the exclusion as narrow as possible.\n\n## Preferred Go exclusion approaches\n\nGo does not provide a stable, official function-level `coverage off` attribute equivalent to Rust's cargo-llvm-cov cfg-gated `coverage(off)` usage.\n\nDo not invent source comments such as:\n\n```go id=\"s33s5w\"\n\u002F\u002F coverage:ignore\n```\n\nor:\n\n```go id=\"kk7sq2\"\n\u002F\u002Fgo:coverage off\n```\n\nunless the repository already has an explicit, documented tool that consumes those comments.\n\nPrefer the following approaches, in this order.\n\n### 1. Move test-only helpers into `_test.go`\n\nIf the code exists only for tests, fixtures, or test scaffolding, move it into a `_test.go` file when possible.\n\nExample:\n\n```go id=\"lsczgq\"\npackage parser\n\nfunc newFixtureParser() *Parser {\n\treturn &Parser{\n\t\t\u002F\u002F test-only setup\n\t}\n}\n```\n\nThis is preferable when the code is not needed by production builds.\n\n### 2. Isolate verification-only code into a separate package or directory\n\nIf a builtin, fixture, generator, or validation helper is not part of production behavior, isolate it so the coverage command can exclude it explicitly.\n\nExample directory layout:\n\n```text id=\"k37v0k\"\ninternal\u002F\n  builtin\u002F\n    production_builtin.go\n  verificationbuiltin\u002F\n    fixture_builtin.go\n```\n\nThen configure the repository's coverage command to exclude the verification-only package or directory.\n\n### 3. Use build tags only when the file truly belongs to a separate build mode\n\nUse `\u002F\u002Fgo:build` only when the file should be included or excluded based on a real build mode.\n\nExample:\n\n```go id=\"lb5hcj\"\n\u002F\u002Fgo:build verification\n\npackage verificationbuiltin\n```\n\nDo not use build tags merely to hide poorly tested production code from coverage.\n\nIf build tags are used for verification-only code, the Makefile must make the intended mode explicit.\n\nExample:\n\n```makefile id=\"ks27zx\"\ntest:\n\tgo test .\u002F...\n\ntest-verification:\n\tgo test -tags=verification .\u002F...\n```\n\n### 4. Filter the coverage profile only as an explicit repository policy\n\nIf the repository needs to exclude generated or verification-only files from a coverage report, do it in the Makefile or a dedicated coverage script by filtering the coverage profile.\n\nExample:\n\n```makefile id=\"6dz9nn\"\ncoverage.out:\n\tgo test .\u002F... -coverprofile=coverage.raw.out\n\tgrep -vE '\u002Finternal\u002Fverificationbuiltin\u002F|_generated\\.go' coverage.raw.out > coverage.out\n\tgo tool cover -func=coverage.out\n```\n\nThe filtering pattern must be narrow and documented.\n\nDo not silently filter broad paths such as all of `internal\u002F` or all files containing `builtin` unless the repository has explicitly decided that those paths are outside the coverage target.\n\n## Coverage exclusion documentation\n\nEvery coverage exclusion must include a short explanation in the relevant code, Makefile, or coverage script.\n\nThe explanation must state:\n\n* what is being excluded\n* why adding tests would not be meaningful\n* why the exclusion is narrower than the alternative\n* whether the excluded code is production code, generated code, fixture code, or verification-only code\n\nExample:\n\n```makefile id=\"tt43hm\"\n# Exclude internal\u002Fverificationbuiltin from coverage because it contains\n# fixture-only builtin implementations used to validate the evaluator contract.\n# Production builtin behavior remains covered under internal\u002Fbuiltin.\nCOVERAGE_EXCLUDE := \u002Finternal\u002Fverificationbuiltin\u002F\n```\n\n## Completion criteria\n\nThe task is complete only when:\n\n* the requested Go implementation change is made\n* relevant tests are added or updated when behavior changes\n* coverage failures are resolved by tests or justified narrow exclusions\n* `just check` succeeds\n* the final report states what was changed and that `just check` passed\n\nDo not claim success unless `just check` was actually run successfully.\n","# go-make-check-verification\n\n## Purpose\n\nEnsure that every Go implementation change is verified by the repository's standard check command, and that coverage failures are resolved by improving tests unless there is a justified reason to exclude verification-only code from coverage.\n\n## When to use this skill\n\nUse this skill whenever you modify Go implementation code, Go tests, build configuration, schemas, fixtures, generated code configuration, or coverage-related configuration in this repository.\n\n## Required verification loop\n\nAfter changing implementation or test code, always run:\n\n```sh id=\"cr99o0\"\njust check\n```\n\nIf `just check` fails:\n\n1. Read the error message carefully.\n2. Identify the concrete failing category, such as:\n\n   * formatting failure\n   * lint failure\n   * compile failure\n   * unit test failure\n   * integration test failure\n   * schema or fixture validation failure\n   * coverage failure\n3. Fix the cause indicated by the error.\n4. Run `just check` again.\n5. Continue this loop until `just check` succeeds.\n\nDo not treat the task as complete while `just check` is still failing.\n\nIf `just check` cannot be executed because of an environment limitation, missing tool, missing permission, network restriction, or external service failure, stop and report:\n\n* the exact command attempted\n* the exact error output\n* whether the failure is caused by the repository code or by the execution environment\n* the remaining unverified risk\n\n## Go coverage policy\n\nIf coverage is low or a coverage threshold fails, first assume the correct response is to add or improve tests.\n\nPrefer tests that cover observable behavior rather than tests that merely execute lines for the sake of increasing coverage.\n\nWhen adding tests, prioritize:\n\n1. public behavior and CLI-visible behavior\n2. parser \u002F evaluator \u002F reporter boundaries\n3. error cases and validation failures\n4. regression cases related to the change being made\n5. edge cases that are likely to break silently\n6. package boundary behavior, especially when interfaces or adapters are involved\n\nDo not lower the coverage threshold merely to make the check pass.\n\n## Go coverage exclusion policy\n\nCoverage exclusion is allowed only when the uncovered code is primarily verification-only, scaffolding-only, generated, or structurally unsuitable for meaningful behavioral testing.\n\nExamples that may be eligible:\n\n* builtin module implementations used mainly as validation scaffolding\n* generated code\n* test-only adapters\n* fixture-only helpers\n* code that exists only to support schema or artifact validation\n* unreachable defensive branches that cannot be exercised without corrupting invariants\n\nBefore excluding code from coverage, confirm that adding a meaningful test would not be the better fix.\n\nWhen excluding code, keep the exclusion as narrow as possible.\n\n## Preferred Go exclusion approaches\n\nGo does not provide a stable, official function-level `coverage off` attribute equivalent to Rust's cargo-llvm-cov cfg-gated `coverage(off)` usage.\n\nDo not invent source comments such as:\n\n```go id=\"s33s5w\"\n\u002F\u002F coverage:ignore\n```\n\nor:\n\n```go id=\"kk7sq2\"\n\u002F\u002Fgo:coverage off\n```\n\nunless the repository already has an explicit, documented tool that consumes those comments.\n\nPrefer the following approaches, in this order.\n\n### 1. Move test-only helpers into `_test.go`\n\nIf the code exists only for tests, fixtures, or test scaffolding, move it into a `_test.go` file when possible.\n\nExample:\n\n```go id=\"lsczgq\"\npackage parser\n\nfunc newFixtureParser() *Parser {\n\treturn &Parser{\n\t\t\u002F\u002F test-only setup\n\t}\n}\n```\n\nThis is preferable when the code is not needed by production builds.\n\n### 2. Isolate verification-only code into a separate package or directory\n\nIf a builtin, fixture, generator, or validation helper is not part of production behavior, isolate it so the coverage command can exclude it explicitly.\n\nExample directory layout:\n\n```text id=\"k37v0k\"\ninternal\u002F\n  builtin\u002F\n    production_builtin.go\n  verificationbuiltin\u002F\n    fixture_builtin.go\n```\n\nThen configure the repository's coverage command to exclude the verification-only package or directory.\n\n### 3. Use build tags only when the file truly belongs to a separate build mode\n\nUse `\u002F\u002Fgo:build` only when the file should be included or excluded based on a real build mode.\n\nExample:\n\n```go id=\"lb5hcj\"\n\u002F\u002Fgo:build verification\n\npackage verificationbuiltin\n```\n\nDo not use build tags merely to hide poorly tested production code from coverage.\n\nIf build tags are used for verification-only code, the Makefile must make the intended mode explicit.\n\nExample:\n\n```makefile id=\"ks27zx\"\ntest:\n\tgo test .\u002F...\n\ntest-verification:\n\tgo test -tags=verification .\u002F...\n```\n\n### 4. Filter the coverage profile only as an explicit repository policy\n\nIf the repository needs to exclude generated or verification-only files from a coverage report, do it in the Makefile or a dedicated coverage script by filtering the coverage profile.\n\nExample:\n\n```makefile id=\"6dz9nn\"\ncoverage.out:\n\tgo test .\u002F... -coverprofile=coverage.raw.out\n\tgrep -vE '\u002Finternal\u002Fverificationbuiltin\u002F|_generated\\.go' coverage.raw.out > coverage.out\n\tgo tool cover -func=coverage.out\n```\n\nThe filtering pattern must be narrow and documented.\n\nDo not silently filter broad paths such as all of `internal\u002F` or all files containing `builtin` unless the repository has explicitly decided that those paths are outside the coverage target.\n\n## Coverage exclusion documentation\n\nEvery coverage exclusion must include a short explanation in the relevant code, Makefile, or coverage script.\n\nThe explanation must state:\n\n* what is being excluded\n* why adding tests would not be meaningful\n* why the exclusion is narrower than the alternative\n* whether the excluded code is production code, generated code, fixture code, or verification-only code\n\nExample:\n\n```makefile id=\"tt43hm\"\n# Exclude internal\u002Fverificationbuiltin from coverage because it contains\n# fixture-only builtin implementations used to validate the evaluator contract.\n# Production builtin behavior remains covered under internal\u002Fbuiltin.\nCOVERAGE_EXCLUDE := \u002Finternal\u002Fverificationbuiltin\u002F\n```\n\n## Completion criteria\n\nThe task is complete only when:\n\n* the requested Go implementation change is made\n* relevant tests are added or updated when behavior changes\n* coverage failures are resolved by tests or justified narrow exclusions\n* `just check` succeeds\n* the final report states what was changed and that `just check` passed\n\nDo not claim success unless `just check` was actually run successfully.\n",{"name":5,"description":7},"main","cce1a97288e4d9b521d0fc45506ed2180e15388d",".claude\u002Fskills\u002Fcode-fix",1,"https:\u002F\u002Fgithub.com\u002Ftooppoo\u002Fgit-kura","https:\u002F\u002Fgithub.com\u002Ftooppoo","https:\u002F\u002Fphilomagi.dev\u002F","2026-09-15 00:17:26",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add tooppoo\u002Fgit-kura --skill code-fix",{"tool":38,"command":39},"bunx","bunx skills add tooppoo\u002Fgit-kura --skill code-fix",{"tool":41,"command":42},"pnpm","pnpm dlx skills add tooppoo\u002Fgit-kura --skill code-fix","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftooppoo\u002Fgit-kura\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcode-fix\u002FSKILL.md",true,[],[47,54,59,66,71,78],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M75DCYR6JKWV99NXBKSHG8R3","git-kura","Use git-kura to manage task worktrees, path seals, and tool components safely. Activate for review work or any repository file-changing task — implementing features, updating docs, adding tests, refactoring — in a git-kura-managed repository, even when the user does not mention git-kura explicitly.","https:\u002F\u002Fgithub.com\u002Ftooppoo\u002Fgit-kura\u002Fblob\u002Fmain\u002Ftools\u002Fskills\u002Fcodex\u002FSKILL.md",[],[],{"skillNo":55,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M75DCVY7M33BDQCSMFE0712E","https:\u002F\u002Fgithub.com\u002Ftooppoo\u002Fgit-kura\u002Fblob\u002Fmain\u002Ftools\u002Fskills\u002Fclaude\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M75DCRFW606VGXYA9BQ6ZQ00","read-issue","Read a GitHub Issue as the authoritative task context by checking the issue body, all comments, explicit Finalized comments, and ADR Plan comments before acting.","https:\u002F\u002Fgithub.com\u002Ftooppoo\u002Fgit-kura\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fread-issue\u002FSKILL.md",[],[],{"skillNo":67,"name":49,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M75DCQ041YHJ3VETNCF4BB1X","https:\u002F\u002Fgithub.com\u002Ftooppoo\u002Fgit-kura\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fgit-kura\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M75DCN0PD6ZA91TK8D3SEXRR","documentation","git-kura の README や docs を作成・更新するときに使う documentation skill。 docs\u002Fadr 配下に ADR を作るとき、既存ドキュメントを変更するとき、またはドキュメント間の矛盾を検証するときに必ず参照すること。 文中で prose を途中改行せず、ADR は docs\u002Fadr\u002FTEMPLATE.md と docs\u002Fadr\u002FREADME.md に従う。","https:\u002F\u002Fgithub.com\u002Ftooppoo\u002Fgit-kura\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fdocumentation\u002FSKILL.md",[],[],{"skillNo":79,"name":61,"nameZh":6,"description":62,"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":19},"01M75DCCKWZNSC6427XT9NVVDW","https:\u002F\u002Fgithub.com\u002Ftooppoo\u002Fgit-kura\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fread-issue\u002FSKILL.md",[],[]]