[{"_1":2,"_290":-5,"_291":-5},"loaderData",{"_3":4,"_8":9,"_23":24},"root",{"_5":-5,"_6":7},"user","countable",false,"routes/_main",{"_5":-5,"_10":11},"recentPosts",[12,17,20],{"_13":14,"_15":16},"slug","claude-code-agent-teams","title","What Claude Code's Agent Teams Feature Does",{"_13":18,"_15":19},"claude-code-goal-command","How Claude Code's /goal Command Works",{"_13":21,"_15":22},"claude-code-routines-vs-loop","Claude Code Routines vs /loop: What's the Difference?","routes/creators.$handle",{"_25":26,"_27":26,"_28":29,"_30":7,"_31":32,"_288":7,"_289":99},"handle","agno-agi","displayName","profileUrl","https://github.com/agno-agi","verified","skills",[33],{"_34":35,"_13":36,"_37":38,"_39":40,"_41":42,"_43":44,"_45":46,"_47":48,"_49":50,"_51":52,"_53":54,"_60":56,"_61":62,"_63":64,"_79":80,"_81":-5,"_82":83,"_84":85,"_86":87,"_88":89,"_90":91,"_92":-5,"_93":94,"_95":26,"_30":7,"_96":7,"_97":85,"_98":99,"_100":85,"_101":85,"_102":103,"_104":105,"_134":135,"_172":173,"_223":224,"_260":261,"_272":273,"_284":285,"_286":287},"id","gh__agno-agi__agno__cookbook-02-agents-16-skills-sample-skills-git-workflow","git-workflow-agno-agi","name","Git Workflow","canonicalName","git-workflow","tagline","Streamline your Git commits, branches, and pull requests.","description","Git workflow guidance for commits, branches, and pull requests","longDescription","The Git Workflow skill is designed to assist developers in managing their Git operations efficiently by providing structured guidelines for commits, branch naming, and pull requests. By adhering to best practices, this skill helps maintain a clean and organized version control history, which is essential for collaborative software development. It offers a clear format for commit messages, ensuring that each commit is informative and easy to understand, which is crucial for tracking changes over time.\n\nThis skill includes a script for generating and validating commit messages based on predefined types such as 'feat', 'fix', and 'chore'. These types help categorize changes effectively, making it easier for team members to comprehend the purpose of each commit. Additionally, the skill provides a standardized naming convention for branches, which aids in identifying the purpose of a branch at a glance. This organization is particularly useful in larger projects where multiple features and fixes are being developed simultaneously.\n\nFor pull requests, the skill outlines a comprehensive template to ensure that all necessary information is included. This includes a summary of changes, testing details, and a checklist to confirm that all relevant tasks have been completed. By following these guidelines, developers can create clear and concise pull requests that facilitate smoother code reviews and integration into the main codebase.\n\nOverall, the Git Workflow skill is an invaluable tool for developers looking to enhance their Git practices, improve collaboration, and maintain high code quality throughout the development lifecycle.","primaryCategory","development","subcategory","version-control","secondaryCategories",[],"tags",[55,56,57,58,59],"git","workflow","commit-messages","pull-requests","branch-naming","skillType","complexity","intermediate","platforms",[65,66,67,68,69,70,71,72,73,74,75,76,77,78],"claude-code","claude-api","codex-cli","cursor","antigravity","github-copilot","windsurf","opencode","cline","roo-code","goose","kiro","continue","trae","delivery","source-link","skillFileUrl","pricing","free","price",0,"thumbnailType","icon","thumbnailIcon","git-branch","thumbnailColor","blue","thumbnailImageUrl","sellerId","gh__agno-agi","sellerName","featured","downloads","views",1,"rating","reviewCount","status","active","metrics",{"_106":107,"_108":99,"_109":110,"_111":112,"_113":85,"_114":115,"_116":117,"_118":119,"_120":121,"_122":123,"_124":125,"_126":127,"_128":129,"_130":131,"_132":133},"freshnessScore",100,"mirrorCount","skillCountInRepo",4,"qualityScore",75,"daysSinceUpdate","popularityScore",95,"trustScore",65,"repoOpenIssues",1211,"repoStars",41649,"repoWatchers",237,"repoContributors",526,"overallScore",82,"repoCreatedAt","2022-05-04T15:23:02Z","repoForks",5751,"repoPushedAt","2026-08-11T00:28:31Z","source",{"_136":26,"_137":138,"_139":140,"_145":146,"_147":148,"_149":-5,"_143":150,"_151":152,"_153":146,"_154":7,"_155":156,"_157":158,"_164":165,"_166":167,"_168":169,"_170":171},"owner","repoUrl","https://github.com/agno-agi/agno","author",{"_28":29,"_141":142,"_37":26,"_25":26,"_143":144},"avatarUrl","https://github.com/agno-agi.png","type","User","lastSyncedAt","2026-08-11T01:33:45.743Z","repo","agno","commitSha","github","branch","main","firstSeenAt","isOfficial","path","cookbook/02_agents/16_skills/sample_skills/git-workflow","license",{"_37":159,"_160":161,"_162":163},"Apache License 2.0","spdxId","Apache-2.0","url","https://github.com/agno-agi/agno/blob/main/LICENSE","sourceUpdatedAt","2026-08-10T23:58:13.000Z","redistributable",true,"permalink","https://github.com/agno-agi/agno/blob/main/cookbook/02_agents/16_skills/sample_skills/git-workflow/SKILL.md","repoFullName","agno-agi/agno","seo",{"_174":175,"_186":187,"_188":189,"_207":-5,"_208":209,"_215":216,"_217":218,"_219":220,"_221":222},"useCases",[176,180,183],{"_15":177,"_178":179},"Generating Commit Messages","body","Use the skill to create well-structured commit messages that follow best practices, improving code clarity.",{"_15":181,"_178":182},"Organizing Branches","Adopt the branch naming conventions provided to keep your feature and fix branches organized and easy to identify.",{"_15":184,"_178":185},"Creating Pull Requests","Utilize the pull request template to ensure all necessary information is included, facilitating smoother code reviews.","whenNotToUse","This skill may not be suitable for users who prefer a more flexible or informal approach to version control.","faqs",[190,195,198,201,204],{"_191":192,"_193":194},"q","What types of commit messages does this skill support?","a","The skill supports several commit message types including 'feat', 'fix', 'docs', 'style', 'refactor', 'perf', 'test', and 'chore', helping categorize changes effectively.",{"_191":196,"_193":197},"How do I generate a commit message using this skill?","You can generate a commit message by using the provided script `commit_message.py`, which follows the specified format for commit messages.",{"_191":199,"_193":200},"What is the recommended format for branch names?","Branch names should follow the format `/-`, such as `feature/AUTH-123-oauth-login`.",{"_191":202,"_193":203},"Are there templates for pull requests?","Yes, the skill provides a pull request description template that includes sections for summary, changes, testing, and a checklist.",{"_191":205,"_193":206},"Can I use this skill for solo projects?","While this skill is designed with collaboration in mind, it can also help individuals maintain a structured approach to version control.","ogImageUrl","keywords",[210,211,212,213,214],"git workflow","commit message guidelines","branch naming","pull request templates","git best practices","whenToUse","Use this skill when you need structured guidance for managing Git workflows in a collaborative environment.","metaTitle","Git Workflow - Streamline Your Git Operations","problemSolved","This skill removes the confusion around Git commit messages, branch naming, and pull request creation.","metaDescription","Enhance your Git practices with structured commit, branch, and PR guidelines. Improve collaboration today!","content",{"_225":226,"_227":228,"_243":244,"_253":254,"_255":7,"_256":257,"_258":259},"bundledFiles",2,"fileTree",[229,236,239],{"_155":230,"_231":232,"_143":233,"_234":235},"SKILL.md","size",2207,"file","language","markdown",{"_155":237,"_231":238,"_143":233,"_234":235},"references/commit-types.md",1999,{"_155":240,"_231":241,"_143":233,"_234":242},"scripts/commit_message.py",3720,"python","codeExamples",[245,249,251],{"_234":246,"_247":248},"text","snippet","(): \n\n\n\n