[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79ZC7B5R0CHZ615VMDAQSTF":3,"skill-same:01M79ZC7B5R0CHZ615VMDAQSTF":52},{"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":31,"commitSha":32,"skillDirectory":33,"forksCount":14,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":36,"ownerDescription":37,"updatedAt":38,"install":39,"resources":51},"01M79ZC7B5R0CHZ615VMDAQSTF","git-commit",null,"Structured git commit messages following Conventional Commits format for Go projects. Generates well-scoped, atomic commits with clear descriptions. Use when committing changes, writing commit messages, preparing PRs, or reviewing commit history quality. Trigger examples: \"commit these changes\", \"create commit\", \"commit message\", \"prepare PR\", \"squash commits\". Not for: code review (go-code-review), changelog generation.","kongnakornna\u002Fgolangapi","kongnakornna","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F10528904?v=4","01M79Z5JQPPV5CWQHXS235Q9MD","Kongnakorn Jantakun","01M79Z5JRHJJJ6PR2DGQS4P985",0,"MIT","https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fgo-agent-skills\u002Fskills\u002F(workflow)\u002Fgit-commit\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: git-commit\ndescription: >\n  Structured git commit messages following Conventional Commits format for\n  Go projects. Generates well-scoped, atomic commits with clear\n  descriptions. Use when committing changes, writing commit messages,\n  preparing PRs, or reviewing commit history quality. Trigger examples:\n  \"commit these changes\", \"create commit\", \"commit message\", \"prepare PR\",\n  \"squash commits\".\n  Not for: code review (go-code-review), changelog generation.\nuser-invocable: true\nlicense: MIT\ncompatibility: Designed for Claude Code or similar AI coding agents. Requires git.\nallowed-tools: Read Glob Grep Bash(git:*)\nmetadata:\n  author: eduardo-sl\n  version: \"1.2.1\"\n---\n\n# Git Commit Standards\n\nCommits tell the story of your codebase. A good commit history is worth\nmore than any amount of documentation — because it's always up to date.\n\n## 1. Conventional Commits Format\n\n```text\n\u003Ctype>(\u003Cscope>): \u003Cdescription>\n\n[optional body]\n\n[optional footer(s)]\n```\n\n### Types:\n\n| Type | When |\n|---|---|\n| `feat` | New feature (correlates with MINOR in semver) |\n| `fix` | Bug fix (correlates with PATCH in semver) |\n| `refactor` | Code change that neither fixes a bug nor adds a feature |\n| `perf` | Performance improvement |\n| `test` | Adding or correcting tests |\n| `docs` | Documentation changes only |\n| `chore` | Build process, tooling, dependencies |\n| `ci` | CI\u002FCD configuration changes |\n| `style` | Formatting, whitespace (not CSS — code formatting) |\n\n### Scope:\n\nUse the package name or module area:\n\n```text\nfeat(auth): add JWT refresh token rotation\nfix(store\u002Fpostgres): handle connection pool exhaustion\nrefactor(service): extract validation into dedicated package\ntest(handler): add table-driven tests for user endpoints\nchore(deps): bump go.uber.org\u002Fzap to v1.27.0\n```\n\n### Breaking changes:\n\n```text\nfeat(api)!: change pagination from offset to cursor-based\n\nBREAKING CHANGE: The `offset` and `limit` query parameters are replaced\nby `cursor` and `page_size`. All existing clients must migrate.\n```\n\n## 2. Commit Message Rules\n\n### Subject line:\n- Imperative mood: \"add feature\", NOT \"added feature\" or \"adds feature\"\n- Lowercase after type prefix\n- No period at the end\n- Max 72 characters\n- Must describe WHAT changed, not HOW\n\n### Body (when needed):\n- Blank line between subject and body\n- Explain WHY the change was necessary\n- Explain WHAT is different at a high level\n- Wrap at 72 characters\n\n### Footer:\n- Reference issues: `Fixes #123`, `Closes #456`, `Refs #789`\n- Co-authors: `Co-authored-by: Name \u003Cemail>`\n- Breaking changes: `BREAKING CHANGE: description`\n\n## 3. Examples\n\n### Simple change:\n\n```text\nfix(handler): return 404 instead of 500 for missing user\n```\n\n### With body:\n\n```text\nrefactor(service): replace manual SQL with sqlx named queries\n\nThe raw SQL string concatenation for dynamic WHERE clauses was\nerror-prone and difficult to maintain. sqlx named queries provide\nthe same flexibility with automatic parameter binding.\n\nNo behavior change — all existing tests pass.\n```\n\n### Breaking change:\n\n```text\nfeat(config)!: migrate from YAML to environment variables\n\nBREAKING CHANGE: Configuration is now loaded from environment\nvariables instead of config.yaml. See README.md for the full\nlist of supported variables.\n\nCloses #234\n```\n\n### Dependency update:\n\n```text\nchore(deps): upgrade pgx to v5.5.0\n\nPicks up connection pool improvements and fixes for\nCOPY protocol handling. See release notes:\nhttps:\u002F\u002Fgithub.com\u002Fjackc\u002Fpgx\u002Freleases\u002Ftag\u002Fv5.5.0\n```\n\n## 4. Atomic Commits\n\nEach commit should be ONE logical change that:\n- Compiles on its own (`go build .\u002F...` passes)\n- Tests pass (`go test .\u002F...` passes)\n- Can be reverted independently without breaking other changes\n\n### Split large changes:\n\n```text\n# ❌ Bad — one commit doing everything\nfeat(user): add user management with CRUD, validation, auth, and tests\n\n# ✅ Good — atomic, reviewable commits\nfeat(domain): add User entity and validation rules\nfeat(store): implement PostgreSQL user repository\nfeat(service): add user service with create and get operations\nfeat(handler): add REST endpoints for user management\ntest(service): add table-driven tests for user creation\ndocs(api): document user endpoints in OpenAPI spec\n```\n\n## 5. Pre-Commit Verification\n\nBefore committing, run:\n\n```bash\n# Format and lint\ngoimports -w .\ngolangci-lint run\n\n# Build\ngo build .\u002F...\n\n# Test\ngo test -race .\u002F...\n\n# Tidy modules\ngo mod tidy\n```\n\nIf any step fails, fix before committing. Never commit broken code\nwith \"will fix later\" — you won't.\n\n## 6. Commit Workflow\n\n```bash\n# Stage specific files (not git add .)\ngit add internal\u002Fservice\u002Fuser.go\ngit add internal\u002Fservice\u002Fuser_test.go\n\n# Review staged changes\ngit diff --staged\n\n# Commit with message\ngit commit -m \"feat(service): add user creation with email validation\"\n\n# Or use editor for longer messages\ngit commit  # opens $EDITOR\n```\n\n### Interactive rebase before PR:\n\nInteractive rebase opens `$EDITOR`, so an agent cannot drive it. Prepare\nfixups non-interactively, then hand the final step to the developer:\n\n```bash\n# Mark a commit as a fixup of an earlier one (no editor)\ngit commit --fixup \u003Csha>\n\n# Collapse them automatically (no editor with --autosquash + GIT_SEQUENCE_EDITOR)\nGIT_SEQUENCE_EDITOR=: git rebase -i --autosquash main\n```\n\nFor reordering or rewording, tell the developer to run `git rebase -i main`\nthemselves rather than attempting it.\n\n## 7. What NOT to Commit\n\n- Generated files (`*.pb.go` unless required, `mocks\u002F`)\n- IDE configuration (`.idea\u002F`, `.vscode\u002F` — use global gitignore)\n- OS files (`.DS_Store`, `Thumbs.db`)\n- Binaries and build artifacts\n- `.env` files with secrets\n- `vendor\u002F` (unless explicitly required by project policy)\n","# Git Commit Standards\n\nCommits tell the story of your codebase. A good commit history is worth\nmore than any amount of documentation — because it's always up to date.\n\n## 1. Conventional Commits Format\n\n```text\n\u003Ctype>(\u003Cscope>): \u003Cdescription>\n\n[optional body]\n\n[optional footer(s)]\n```\n\n### Types:\n\n| Type | When |\n|---|---|\n| `feat` | New feature (correlates with MINOR in semver) |\n| `fix` | Bug fix (correlates with PATCH in semver) |\n| `refactor` | Code change that neither fixes a bug nor adds a feature |\n| `perf` | Performance improvement |\n| `test` | Adding or correcting tests |\n| `docs` | Documentation changes only |\n| `chore` | Build process, tooling, dependencies |\n| `ci` | CI\u002FCD configuration changes |\n| `style` | Formatting, whitespace (not CSS — code formatting) |\n\n### Scope:\n\nUse the package name or module area:\n\n```text\nfeat(auth): add JWT refresh token rotation\nfix(store\u002Fpostgres): handle connection pool exhaustion\nrefactor(service): extract validation into dedicated package\ntest(handler): add table-driven tests for user endpoints\nchore(deps): bump go.uber.org\u002Fzap to v1.27.0\n```\n\n### Breaking changes:\n\n```text\nfeat(api)!: change pagination from offset to cursor-based\n\nBREAKING CHANGE: The `offset` and `limit` query parameters are replaced\nby `cursor` and `page_size`. All existing clients must migrate.\n```\n\n## 2. Commit Message Rules\n\n### Subject line:\n- Imperative mood: \"add feature\", NOT \"added feature\" or \"adds feature\"\n- Lowercase after type prefix\n- No period at the end\n- Max 72 characters\n- Must describe WHAT changed, not HOW\n\n### Body (when needed):\n- Blank line between subject and body\n- Explain WHY the change was necessary\n- Explain WHAT is different at a high level\n- Wrap at 72 characters\n\n### Footer:\n- Reference issues: `Fixes #123`, `Closes #456`, `Refs #789`\n- Co-authors: `Co-authored-by: Name \u003Cemail>`\n- Breaking changes: `BREAKING CHANGE: description`\n\n## 3. Examples\n\n### Simple change:\n\n```text\nfix(handler): return 404 instead of 500 for missing user\n```\n\n### With body:\n\n```text\nrefactor(service): replace manual SQL with sqlx named queries\n\nThe raw SQL string concatenation for dynamic WHERE clauses was\nerror-prone and difficult to maintain. sqlx named queries provide\nthe same flexibility with automatic parameter binding.\n\nNo behavior change — all existing tests pass.\n```\n\n### Breaking change:\n\n```text\nfeat(config)!: migrate from YAML to environment variables\n\nBREAKING CHANGE: Configuration is now loaded from environment\nvariables instead of config.yaml. See README.md for the full\nlist of supported variables.\n\nCloses #234\n```\n\n### Dependency update:\n\n```text\nchore(deps): upgrade pgx to v5.5.0\n\nPicks up connection pool improvements and fixes for\nCOPY protocol handling. See release notes:\nhttps:\u002F\u002Fgithub.com\u002Fjackc\u002Fpgx\u002Freleases\u002Ftag\u002Fv5.5.0\n```\n\n## 4. Atomic Commits\n\nEach commit should be ONE logical change that:\n- Compiles on its own (`go build .\u002F...` passes)\n- Tests pass (`go test .\u002F...` passes)\n- Can be reverted independently without breaking other changes\n\n### Split large changes:\n\n```text\n# ❌ Bad — one commit doing everything\nfeat(user): add user management with CRUD, validation, auth, and tests\n\n# ✅ Good — atomic, reviewable commits\nfeat(domain): add User entity and validation rules\nfeat(store): implement PostgreSQL user repository\nfeat(service): add user service with create and get operations\nfeat(handler): add REST endpoints for user management\ntest(service): add table-driven tests for user creation\ndocs(api): document user endpoints in OpenAPI spec\n```\n\n## 5. Pre-Commit Verification\n\nBefore committing, run:\n\n```bash\n# Format and lint\ngoimports -w .\ngolangci-lint run\n\n# Build\ngo build .\u002F...\n\n# Test\ngo test -race .\u002F...\n\n# Tidy modules\ngo mod tidy\n```\n\nIf any step fails, fix before committing. Never commit broken code\nwith \"will fix later\" — you won't.\n\n## 6. Commit Workflow\n\n```bash\n# Stage specific files (not git add .)\ngit add internal\u002Fservice\u002Fuser.go\ngit add internal\u002Fservice\u002Fuser_test.go\n\n# Review staged changes\ngit diff --staged\n\n# Commit with message\ngit commit -m \"feat(service): add user creation with email validation\"\n\n# Or use editor for longer messages\ngit commit  # opens $EDITOR\n```\n\n### Interactive rebase before PR:\n\nInteractive rebase opens `$EDITOR`, so an agent cannot drive it. Prepare\nfixups non-interactively, then hand the final step to the developer:\n\n```bash\n# Mark a commit as a fixup of an earlier one (no editor)\ngit commit --fixup \u003Csha>\n\n# Collapse them automatically (no editor with --autosquash + GIT_SEQUENCE_EDITOR)\nGIT_SEQUENCE_EDITOR=: git rebase -i --autosquash main\n```\n\nFor reordering or rewording, tell the developer to run `git rebase -i main`\nthemselves rather than attempting it.\n\n## 7. What NOT to Commit\n\n- Generated files (`*.pb.go` unless required, `mocks\u002F`)\n- IDE configuration (`.idea\u002F`, `.vscode\u002F` — use global gitignore)\n- OS files (`.DS_Store`, `Thumbs.db`)\n- Binaries and build artifacts\n- `.env` files with secrets\n- `vendor\u002F` (unless explicitly required by project policy)\n",{"name":5,"license":15,"metadata":24,"description":27,"allowed-tools":28,"compatibility":29,"user-invocable":30},{"author":25,"version":26},"eduardo-sl","1.2.1","Structured git commit messages following Conventional Commits format for Go projects. Generates well-scoped, atomic commits with clear descriptions. Use when committing changes, writing commit messages, preparing PRs, or reviewing commit history quality. Trigger examples: \"commit these changes\", \"create commit\", \"commit message\", \"prepare PR\", \"squash commits\". Not for: code review (go-code-review), changelog generation.\n","Read Glob Grep Bash(git:*)","Designed for Claude Code or similar AI coding agents. Requires git.",true,"main","19f4d52a98d557f3a645a2cfbbeb5bd54f28831d",".github\u002Fskills\u002Fgo-agent-skills\u002Fskills\u002F(workflow)\u002Fgit-commit","https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi","https:\u002F\u002Fgithub.com\u002Fkongnakornna","http:\u002F\u002Fcmoniot.trueddns.com:52160","Technical Skills and Expertise\r\nLanguages and Frameworks\r\nFrontend: HTML, JavaScript, TypeScript, React, Vue, Angular, Next.js\r\nBackend: Node.js,Python,Golang","2026-10-06 23:01:46",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":30},[41,44,47],{"tool":42,"command":43},"npx","npx skills add kongnakornna\u002Fgolangapi --skill git-commit",{"tool":45,"command":46},"bunx","bunx skills add kongnakornna\u002Fgolangapi --skill git-commit",{"tool":48,"command":49},"pnpm","pnpm dlx skills add kongnakornna\u002Fgolangapi --skill git-commit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fgo-agent-skills\u002Fskills\u002F(workflow)\u002Fgit-commit\u002FSKILL.md",[],[53,61,68,75,82,89],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":57,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7A0M9RJJ3383VEFYKABWV15","tb-writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftb-writing-plans\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":57,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7A0M4JKY4DEDRP1CBHT00WV","tb-using-git-worktrees","Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback","https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftb-using-git-worktrees\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":57,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7A0KZ5HRAQAAT2KXR6146Q7","tb-test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftb-test-driven-development\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":57,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7A0KW92W3F18E2MRP8H62P2","tb-subagent-driven-development","Use when executing implementation plans with independent tasks in the current session","https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftb-subagent-driven-development\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":57,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7A0KKYQCHYYRHA5J5BAP24M","tb-scrutinize","Outsider-perspective end-to-end review of a plan, PR, or code change. First questions intent and whether a simpler\u002Fmore elegant approach would achieve the same goal, then traces the actual code path (not just the diff) to verify the change does what it claims. Output is concise, actionable, and every call carries its rationale. Trigger on \u002Ftb-scrutinize and proactively whenever the user asks to review, audit, sanity-check, or get a second opinion on a plan, PR, diff, design doc, or proposed code change.","https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftb-scrutinize\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":57,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M7A0KFDR1V3RW7SW1XNHP82P","tb-requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftb-requesting-code-review\u002FSKILL.md",[],[]]