git-commit Skill
Create standardized git commits with Conventional Commits. Use when the user asks to commit changes, generate a commit message, or at the end of an implementation. Analyzes the actual diff to determine type, scope, and message. Supports logical file grouping and work item references (GitHub Issues and Azure DevOps). Do Published by microsoft in devsquad-copilot.
What is git-commit Skill?
Create standardized git commits with Conventional Commits. Use when the user asks to commit changes, generate a commit message, or at the end of an implementation. Analyzes the actual diff to determine type, scope, and message. Supports logical file grouping and work item references (GitHub Issues and Azure DevOps). Do Published by microsoft in devsquad-copilot. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Testing
- Deployment
- Documentation
- Writing
- Testing use cases
Technical details
- Install or run with Copy skill directory
When to use git-commit Skill
- Use it for testing.
- Use it for deployment.
- Use it for documentation.
- Use it for writing.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/devsquad-copilot
- Skill file: .github/plugins/devsquad/skills/git-commit/SKILL.md
What it does
Create standardized git commits with Conventional Commits. Use when the user asks to commit changes, generate a commit message, or at the end of an implementation. Analyzes the actual diff to determine type, scope, and message. Supports logical file grouping and work item references (GitHub Issues and Azure DevOps). Do
Skill instructions
Git Commit — Conventional Commits for SDD Format <type[optional scope]: <description [optional body] [optional footer] References: Conventional Commits and How to Write a Git Commit Message. Commit Types | Type | Usage | |------|-------| | feat | New feature | | fix | Bug fix | | docs | Documentation-only change | | style | Formatting, semicolons, whitespace (no logic change) | | refactor | Refactoring without behavior change | | perf | Performance improvement | | test | Adding or fixing tests | | build | Build system or external dependencies | | ci | CI/CD configuration | | chore | General maintenance (scripts, configs) | | revert | Revert a previous commit | Mapping to SDD Artifacts | SDD Artifact | Likely type | |---|---| | docs/features//spec.md | docs | | docs/architecture/decisions/.md (ADR) | docs | | tasks.md, work items | docs or chore | | Implementation code | feat, fix, refactor, perf | | Tests | test | | Agents, skills, instructions (.github/) | chore or ci | Breaking Chang
Explore related resources
Frequently asked questions
What is git-commit?
git-commit is a open-source AI agent skill with Copy skill directory. Create standardized git commits with Conventional Commits. Use when the user asks to commit changes, generate a commit message, or at the end of an implementation.
Who is git-commit best for?
git-commit is best for reusing agent instructions, scripts, and references, testing workflows, deployment workflows, documentation workflows.
How do I install git-commit?
Install or run git-commit using Copy skill directory. Check git-commit for the latest setup command.
Is git-commit actively maintained?
git-commit may need a closer maintenance check before production use.
Auto-fetched from GitHub.
