[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FC4GKWFFCJNJTYT7BGR0C3":3,"skill-same:01M7FC4GKWFFCJNJTYT7BGR0C3":50},{"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":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M7FC4GKWFFCJNJTYT7BGR0C3","git-workflow",null,"Creates branches, small Conventional Commits and pull request descriptions, safely. Use when committing, writing a commit message, creating a branch, pushing, opening or describing a pull request, or resolving a merge conflict.","gustavoSaboia97\u002Fcasulo","gustavoSaboia97","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F28377961?v=4","01M7FC3VEPZE3BH2DBWD0MJ57A","Gustavo Dutra Domingues Saboia","01M7FC3VF9DYHTHHVXZ0GZ630A",0,"GPL-3.0","https:\u002F\u002Fgithub.com\u002FgustavoSaboia97\u002Fcasulo\u002Fblob\u002Fmain\u002Fexamples\u002Fskills\u002Fgit-workflow\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: git-workflow\ndescription: Creates branches, small Conventional Commits and pull request descriptions, safely. Use when committing, writing a commit message, creating a branch, pushing, opening or describing a pull request, or resolving a merge conflict.\n---\n\n# Git workflow\n\nGoal: a history anyone can read and revert, one logical change at a time,\nwithout ever losing someone's work.\n\n## 1. Before starting\n\n- Read the project's rules first (`AGENTS.md`, `CLAUDE.md`, `CONTRIBUTING.md`):\n  they win over this skill.\n- Check where you are: `git status` and `git branch --show-current`.\n- Check the identity commits will carry: `git config user.name` and\n  `git config user.email`. If either is empty, stop and ask the user; never\n  invent or set one yourself.\n- Never work on `main` (or `master`, `develop`). Create a branch from an\n  up-to-date base: `\u003Ctype>\u002F\u003Cshort-description>`, such as `feat\u002Fskill-files`\n  or `fix\u002Fwindows-mount`.\n\n## 2. Commit\n\n1. Review what changed: `git diff`. Stage only files that belong to this\n   change, by name (`git add \u003Cpath>`), not `git add -A` blindly.\n2. Review what is staged: `git diff --staged`. Look for secrets, debug code,\n   generated files and unrelated edits; leave them out.\n3. Run the project's checks (format, lint, tests) before committing.\n4. Commit with `--signoff` (`-s`), always, and a Conventional Commit message.\n   It adds `Signed-off-by: \u003Cuser.name> \u003Cuser.email>` from the configured\n   identity:\n\n   ```\n   \u003Ctype>(\u003Coptional scope>): \u003Cwhat changed, imperative, lowercase, no period>\n\n   \u003Cwhy, optional: at most 3 lines>\n   ```\n\n   Keep the subject under 72 characters. Add a body only when the subject\n   does not explain why; then at most 3 short lines on the reason, not on what\n   the diff already shows. No lists of changed files, no long explanations.\n\n   Types: `feat`, `fix`, `docs`, `refactor`, `test`, `chore`, `perf`, `ci`.\n   Add `!` after the type for a breaking change, and explain it in the body.\n\nOne commit is one logical change that builds and passes tests on its own.\nSplit unrelated changes into separate commits; do not mix a refactor with a fix.\n\nCount commits by logical change, never by plan step or by round of review.\nA fix to a commit that is not pushed yet belongs in that commit: commit it\nwith `git commit --signoff --fixup \u003Ccommit>`, then, before you finish, fold\nthe fixups in with `git rebase -i --autosquash \u003Cbase>`, where `\u003Cbase>` is\nthe commit the branch started from (`git merge-base HEAD main`). Set\n`GIT_SEQUENCE_EDITOR=true` when no editor can open. Folding keeps the order\nof the commits, so the branch's last commit stays last. Once a branch is\npushed, add new commits instead.\n\n## 3. Push and pull request\n\n- Push only when the user asked, or the project's rules allow it.\n- Code reaches the server only through `git push`. Never create commits or\n  files through an API (such as the GitHub MCP tools that write files): they\n  skip the signoff, the hooks and the protected branches.\n- If a push is rejected (protected branch, hook), do not work around it:\n  push another branch, or tell the user.\n- Open the pull request with the tool you have for it (the GitHub MCP\n  server, or `gh`). Fill `assets\u002Fpull-request.md` for the description,\n  unless the repository has its own template\n  (`.github\u002Fpull_request_template.md`): then use that.\n- Keep a pull request to one purpose. If it grows, propose splitting it.\n\n## 4. Never, unless the user explicitly asks\n\n- Push to `main` or another protected branch.\n- Rewrite shared history: `push --force`, `rebase` or `commit --amend` on a\n  branch someone else uses. On your own unpushed branch it is fine; prefer\n  `--force-with-lease` if you must.\n- Destroy work: `reset --hard`, `clean -fd`, `checkout -- \u003Cfile>`,\n  `branch -D`. Check `git status` first and say what would be lost.\n- Commit secrets (`.env`, keys, tokens). If one was committed, stop and tell\n  the user: removing it from history is not enough, it must be revoked.\n- Skip hooks or checks (`--no-verify`).\n- Commit without `--signoff`, or with someone else's identity.\n\n## 5. Merge conflicts\n\nMerge the base into the branch (`git merge --signoff origin\u002Fmain`; on\n`merge`, `-s` means strategy, so write `--signoff` in full) rather than\nrebasing a shared branch. Resolve each conflict by understanding both sides;\nif both changed the same logic and keeping either loses behavior, ask the\nuser. Regenerate lockfiles with the project's tool, never by hand. Run the\nchecks again before committing the merge.\n\n## When done\n\nReply in a few lines: branch, commits made (one line each), whether it was\npushed, and the pull request link if one was opened.\n","# Git workflow\n\nGoal: a history anyone can read and revert, one logical change at a time,\nwithout ever losing someone's work.\n\n## 1. Before starting\n\n- Read the project's rules first (`AGENTS.md`, `CLAUDE.md`, `CONTRIBUTING.md`):\n  they win over this skill.\n- Check where you are: `git status` and `git branch --show-current`.\n- Check the identity commits will carry: `git config user.name` and\n  `git config user.email`. If either is empty, stop and ask the user; never\n  invent or set one yourself.\n- Never work on `main` (or `master`, `develop`). Create a branch from an\n  up-to-date base: `\u003Ctype>\u002F\u003Cshort-description>`, such as `feat\u002Fskill-files`\n  or `fix\u002Fwindows-mount`.\n\n## 2. Commit\n\n1. Review what changed: `git diff`. Stage only files that belong to this\n   change, by name (`git add \u003Cpath>`), not `git add -A` blindly.\n2. Review what is staged: `git diff --staged`. Look for secrets, debug code,\n   generated files and unrelated edits; leave them out.\n3. Run the project's checks (format, lint, tests) before committing.\n4. Commit with `--signoff` (`-s`), always, and a Conventional Commit message.\n   It adds `Signed-off-by: \u003Cuser.name> \u003Cuser.email>` from the configured\n   identity:\n\n   ```\n   \u003Ctype>(\u003Coptional scope>): \u003Cwhat changed, imperative, lowercase, no period>\n\n   \u003Cwhy, optional: at most 3 lines>\n   ```\n\n   Keep the subject under 72 characters. Add a body only when the subject\n   does not explain why; then at most 3 short lines on the reason, not on what\n   the diff already shows. No lists of changed files, no long explanations.\n\n   Types: `feat`, `fix`, `docs`, `refactor`, `test`, `chore`, `perf`, `ci`.\n   Add `!` after the type for a breaking change, and explain it in the body.\n\nOne commit is one logical change that builds and passes tests on its own.\nSplit unrelated changes into separate commits; do not mix a refactor with a fix.\n\nCount commits by logical change, never by plan step or by round of review.\nA fix to a commit that is not pushed yet belongs in that commit: commit it\nwith `git commit --signoff --fixup \u003Ccommit>`, then, before you finish, fold\nthe fixups in with `git rebase -i --autosquash \u003Cbase>`, where `\u003Cbase>` is\nthe commit the branch started from (`git merge-base HEAD main`). Set\n`GIT_SEQUENCE_EDITOR=true` when no editor can open. Folding keeps the order\nof the commits, so the branch's last commit stays last. Once a branch is\npushed, add new commits instead.\n\n## 3. Push and pull request\n\n- Push only when the user asked, or the project's rules allow it.\n- Code reaches the server only through `git push`. Never create commits or\n  files through an API (such as the GitHub MCP tools that write files): they\n  skip the signoff, the hooks and the protected branches.\n- If a push is rejected (protected branch, hook), do not work around it:\n  push another branch, or tell the user.\n- Open the pull request with the tool you have for it (the GitHub MCP\n  server, or `gh`). Fill `assets\u002Fpull-request.md` for the description,\n  unless the repository has its own template\n  (`.github\u002Fpull_request_template.md`): then use that.\n- Keep a pull request to one purpose. If it grows, propose splitting it.\n\n## 4. Never, unless the user explicitly asks\n\n- Push to `main` or another protected branch.\n- Rewrite shared history: `push --force`, `rebase` or `commit --amend` on a\n  branch someone else uses. On your own unpushed branch it is fine; prefer\n  `--force-with-lease` if you must.\n- Destroy work: `reset --hard`, `clean -fd`, `checkout -- \u003Cfile>`,\n  `branch -D`. Check `git status` first and say what would be lost.\n- Commit secrets (`.env`, keys, tokens). If one was committed, stop and tell\n  the user: removing it from history is not enough, it must be revoked.\n- Skip hooks or checks (`--no-verify`).\n- Commit without `--signoff`, or with someone else's identity.\n\n## 5. Merge conflicts\n\nMerge the base into the branch (`git merge --signoff origin\u002Fmain`; on\n`merge`, `-s` means strategy, so write `--signoff` in full) rather than\nrebasing a shared branch. Resolve each conflict by understanding both sides;\nif both changed the same logic and keeping either loses behavior, ask the\nuser. Regenerate lockfiles with the project's tool, never by hand. Run the\nchecks again before committing the merge.\n\n## When done\n\nReply in a few lines: branch, commits made (one line each), whether it was\npushed, and the pull request link if one was opened.\n",{"name":5,"description":7},"main","b3235ac1d89c9647507e5697eedf0ca4efb18e47","examples\u002Fskills\u002Fgit-workflow","https:\u002F\u002Fgithub.com\u002FgustavoSaboia97\u002Fcasulo","https:\u002F\u002Fgithub.com\u002FgustavoSaboia97","2026-11-12 03:39:53",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add gustavoSaboia97\u002Fcasulo --skill git-workflow",{"tool":36,"command":37},"bunx","bunx skills add gustavoSaboia97\u002Fcasulo --skill git-workflow",{"tool":39,"command":40},"pnpm","pnpm dlx skills add gustavoSaboia97\u002Fcasulo --skill git-workflow","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FgustavoSaboia97\u002Fcasulo\u002Fblob\u002Fmain\u002Fexamples\u002Fskills\u002Fgit-workflow\u002FSKILL.md",true,[44],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"assets\u002Fpull-request.md","ASSET","资产文件",541,"https:\u002F\u002Fgithub.com\u002FgustavoSaboia97\u002Fcasulo\u002Fblob\u002Fmain\u002Fexamples\u002Fskills\u002Fgit-workflow\u002Fassets\u002Fpull-request.md",[51,58,65,72,79,86],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M7FC535ZW2293Q4925SDA5C4","{name=null}","Describe what {name} does and when the agent should use it","https:\u002F\u002Fgithub.com\u002FgustavoSaboia97\u002Fcasulo\u002Fblob\u002Fmain\u002Ftemplates\u002Fskill.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7FC50ATDXWWH6C86220G7R9","tdd","Develops with TDD driven by BDD scenarios (Given\u002FWhen\u002FThen), writing only the functional, regression and unit tests that protect real behavior. Use when implementing a feature, fixing a bug, or when asked for tests, TDD, BDD, regression tests or coverage.","https:\u002F\u002Fgithub.com\u002FgustavoSaboia97\u002Fcasulo\u002Fblob\u002Fmain\u002Fexamples\u002Fskills\u002Ftdd\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7FC4WJJ6KJM6DEJQWBG16HC","security-audit","Audits code for exploitable security problems (injection, broken access control, leaked secrets, unsafe input handling, vulnerable dependencies) and reports only verified findings with severity and fix. Use when asked for a security review or audit, before a release, or when a change touches authentication, permissions, secrets, user input, file paths, commands or network calls.","https:\u002F\u002Fgithub.com\u002FgustavoSaboia97\u002Fcasulo\u002Fblob\u002Fmain\u002Fexamples\u002Fskills\u002Fsecurity-audit\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7FC4RZ6Q313R8W3J4F58KFZ","requirements","Turns a request or idea into clear, testable requirements, with scope, user stories and Given\u002FWhen\u002FThen acceptance criteria. Use when starting a new feature or project, when a request is vague, or when asked for requirements, user stories, acceptance criteria or a feature spec.","https:\u002F\u002Fgithub.com\u002FgustavoSaboia97\u002Fcasulo\u002Fblob\u002Fmain\u002Fexamples\u002Fskills\u002Frequirements\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7FC4PBM8TXFZGBA9RN3967W","refactoring","Restructures existing code without changing its behavior, in small steps with the tests green after each one. Use when asked to refactor, clean up, simplify, rename, extract, move or reorganize code, or to work on items recorded as \"Refactor later\".","https:\u002F\u002Fgithub.com\u002FgustavoSaboia97\u002Fcasulo\u002Fblob\u002Fmain\u002Fexamples\u002Fskills\u002Frefactoring\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7FC4KEBD4F92H6RMPPZJRZH","implementation-plan","Turns requirements into a short implementation plan of small, verifiable steps, each with the files it touches and the test scenarios it covers. Use after requirements are clear and before coding, or when asked to plan, break down or estimate a change.","https:\u002F\u002Fgithub.com\u002FgustavoSaboia97\u002Fcasulo\u002Fblob\u002Fmain\u002Fexamples\u002Fskills\u002Fimplementation-plan\u002FSKILL.md",[],[]]