How to use
- Copy the installation command and review the source package before installing it in your own agent environment.
- Check the source document for required tools, credentials and supported hosts.
- Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/augmnt/webdev-skills --skill writing-commitsBefore you start
- Installation does not include a model subscription, API allowance or permission to access your files.
- Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document
Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.
Writing Commits
Follow Conventional Commits: <type>(<scope>): <subject>
Types
| Type | Use For |
|---|---|
feat | New user-facing feature |
fix | Bug fix |
docs | Documentation only |
refactor | Code change, no behavior change |
test | Adding/fixing tests |
chore | Build, deps, tooling |
Rules
- Subject: imperative mood, no period, ≤50 chars
- Scope: optional area indicator (auth, api, ui)
- Breaking changes: add
!after type
Examples
bash
feat(auth): add Google OAuth login
fix(api): handle null user in profile endpoint
feat(api)!: change auth response format
chore(deps): upgrade Next.js to 15Anti-patterns
bash
# ❌ Avoid
"fix stuff"
"updates"
"WIP"
# ✅ Prefer
"fix(auth): resolve token refresh race condition"PR Titles
Same format as commits. PR title becomes the squash commit message.
PR Body
markdown
## What
[Brief description]
## Why
[Context/motivation]
## Testing
[How verified]Branch Naming
bash
# Format: type/short-description
feat/oauth-login
fix/token-refresh
chore/upgrade-deps
# With ticket numbers
feat/PROJ-123-oauth-login
fix/PROJ-456-token-refreshKeep branches short-lived. Delete after merge.
