A skill that outlines best practices for using Git in a collaborative development environment, including branching strategies, commit conventions, and pull request workflows.
Provides Git workflow guidance for collaborative development, including branching strategies, commit conventions, and pull request best practices. Claude uses this when users need help with Git operations or team collaboration workflows.
/plugin marketplace add nicholasgriffintn/claude-code/plugin install ng-workflow@claude-codeThis skill is limited to using the following tools:
This skill should only use read-only commands and avoid modifying files.
Copy this checklist and use it to track your progress through the Git workflow process:
Git Workflow Checklist
- [ ] Create a feature branch from the main branch.
- [ ] Make changes and commit frequently with clear, descriptive messages, using atomic commits.
- [ ] Rebase your feature branch onto the latest main branch to keep it up to date.
- [ ] Run tests and ensure all checks pass before pushing changes.
- [ ] Push your feature branch to the remote repository.
- [ ] Open a pull request (PR) against the main branch with a clear description of changes.
- [ ] Request reviews from team members and address any feedback.
- [ ] Once approved, merge the PR using a squash merge to maintain a clean commit history.
- [ ] Delete the feature branch after merging.
Adopt the following branching strategy for effective collaboration:
feature/user-authentication).Here's a visual representation of the branching strategy:
main
|
-----------------
| | |
feature1 feature2 hotfix1
Follow these the Conventional Commits specification for commit messages:
<type>(<scope>): <description>feat: A new featurefix: A bug fixdocs: Documentation changesstyle: Code style changes (formatting, missing semicolons, etc.)refactor: Code changes that neither fix a bug nor add a featuretest: Adding or updating testschore: Maintenance tasks (build process, dependencies, etc.)feat(auth): add user login functionalityWhen creating and managing pull requests, follow these best practices:
Use the following conventions for naming branches:
feature/<descriptive-name>bugfix/<descriptive-name>hotfix/<descriptive-name>release/<version-number>feature/user-authentication, bugfix/login-error, hotfix/payment-issue, release/1.2.0git checkout -b feature/your-feature-name
git add .
git commit -m "feat(scope): descriptive message"
git fetch origin
git rebase origin/main
git push origin feature/your-feature-name
git checkout main
git pull origin main
git merge --squash feature/your-feature-name
git commit -m "Merge feature/your-feature-name"
git push origin main
git branch -d feature/your-feature-name
git push origin --delete feature/your-feature-name
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.