Enforce consistent Git commit types, branch hygiene, and safety rules.
npx skills add https://github.com/Esposter/Esposter --skill git-esposter
Please help me install this Agent Skill. Skill: git Source: https://github.com/Esposter/Esposter/tree/main/.agents/skills/git Command: npx skills add https://github.com/Esposter/Esposter --skill git-esposter
Esposter Git conventions help teams maintain consistent commit messaging, safe branching practices, and robust workflow hygiene to prevent unsafe operations and messy history.
Apply standardized commit messages, maintain branch hygiene, and follow safety rules across your Git workflow.
High-intent search queries and answers about installing and using this skill.
Standardize commit messages by applying conventional commit-like types such as feat, fix, refactor, docs, test, chore, perf, and ci. This keeps your project history readable and consistent across development teams.
The best way to manage Git branches is to enforce branch hygiene rules: create feature branches from develop, target develop for pull requests, and delete branches immediately after merging to streamline reviews and releases.
Prevent data loss during risky Git operations by avoiding stash misuse and preferring WIP commits or git show HEAD:path/to/file for inspection. These safety rules ensure robust workflow hygiene and prevent unsafe operations.
Git history gets messy due to inconsistent commit messaging and unsafe branching practices. You can fix it by specifying commit message types, enforcing branch hygiene, and following strict safety rules across your Git workflow.
Yes, these Git conventions apply to common source-control tasks across development teams and projects. They guide operations and reviews by specifying commit types, safety rules, and branch hygiene requirements for consistent collaboration.
You should avoid git stash misuse when you need to inspect or preserve changes safely. Instead, prefer WIP commits or use git show HEAD:path/to/file to inspect specific files, preventing potential data loss and maintaining clean history.
d0whc3rInitialize a Git repository and create an initial commit.
codekilnValidate worktrees, branch names, issue links, and commit messages for PRs.
eliottbusinessAutomate pre-commit code review with static analysis and security scanning.
mefardalesGuide Git workflows with branching strategies and Conventional Commits.
