{"enrichment":{"faq":[{"a":"git-workflow emphasizes conventional commits format as the foundation for effective commit messages. Structure messages with a type (feat, fix, docs, etc.), optional scope, and clear description. Keep the subject line under 50 characters, use imperative mood, and separate the body with a blank line. This approach enables automated changelog generation and improves team collaboration.","q":"What are git best practices for commit messages?"},{"a":"git-workflow recommends establishing consistent branching conventions tied to purpose: feature branches (feature/description), bugfix branches (bugfix/description), and release branches (release/version). Naming consistency helps teams quickly understand branch intent. Pair this with a clear strategy\u2014gitflow for complex releases or github flow for continuous deployment\u2014based on your team's needs.","q":"How should git-workflow handle branching strategy and naming?"},{"a":"git-workflow advocates for small, focused pull requests that address a single concern, making code review faster and more effective. Include a descriptive PR template, link related issues, and keep discussions constructive. This workflow improves code quality and team communication while reducing merge conflicts and review bottlenecks.","q":"What does git-workflow say about pull request workflow?"},{"a":"git-workflow teaches atomic commits\u2014small, logical units that each represent one change\u2014and interactive rebase for cleanup before merging. Choose merge strategies carefully: rebase for linear history or merge commits for explicit integration points. Clean history makes debugging easier and improves project maintainability.","q":"How does git-workflow keep git history clean?"},{"a":"Yes. git-workflow covers setting up git hooks using tools like Husky and commitlint to validate commits against your standards before they're pushed. Automated enforcement ensures team consistency without manual review, catching formatting issues and preventing non-compliant commits from entering the repository.","q":"Can git-workflow enforce commit standards automatically?"},{"a":"git-workflow explains that rebase rewrites history for a linear, clean timeline\u2014ideal for feature branches before merging to main. Merge commits preserve integration history and are safer for shared branches. Choose based on your workflow: rebase for local cleanup, merge for permanent integration points and collaborative branches.","q":"What's the difference between rebase vs merge in git-workflow?"}],"shadow_tags":["version-control-standards","team-collaboration-workflow","code-review-practices","commit-hygiene","release-management","merge-strategy","branch-lifecycle","automation-hooks","history-integrity"],"summary_rewrite":"git-workflow provides structured guidance on writing effective commit messages using conventional formats, organizing branches by type and purpose, and managing pull requests at scale. It covers atomic commits, conflict resolution, and enforcing standards through git hooks."},"files":[{"bytes":12109,"path":"skills/git-workflow/SKILL.md","sha256":"ea37c193838d664c63f6262b1095cadbdcf1c2b38238d105fa031b074af76706","url":"https://skillfed.io/files/AsyrafHussin/agent-skills/git-workflow/0ac1c830/SKILL.md"}],"id":"AsyrafHussin/agent-skills/git-workflow","links":{"html":"https://skillfed.io/AsyrafHussin/agent-skills/git-workflow","md":"https://skillfed.io/AsyrafHussin/agent-skills/git-workflow.md","repo":"https://github.com/AsyrafHussin/agent-skills"},"meta":{"agents_supported":[],"first_seen":"2026-07-28","forks":9,"language":null,"last_updated":"2026-05-16","license":"MIT","name":"git-workflow","publisher":"AsyrafHussin","stars":58},"relations":{"similar":[{"id":"patricio0312rev/skills/git-hygiene-enforcer"},{"id":"BagelHole/DevOps-Security-Agent-Skills/git-workflow"},{"id":"ScientiaCapital/skills/git-workflow-skill"},{"id":"miles990/claude-software-skills/git-workflows"},{"id":"ancoleman/ai-design-components/managing-git-workflows"},{"id":"samhvw8/dot-claude/git-workflow"},{"id":"samhvw8/dotfiles/git-workflow"},{"id":"pluginagentmarketplace/custom-plugin-data-engineer/git-version-control"},{"id":"jnMetaCode/superpowers-zh/chinese-commit-conventions"},{"id":"jmsktm/claude-settings/git-workflow-designer"}]},"slug":{"owner":"AsyrafHussin","repo":"agent-skills","skill":"git-workflow"},"version":"0ac1c830"}