augmnt/webdev-skills

writing-commits

Generates commit messages and PR descriptions following Conventional Commits.

View source

How to use

  1. Copy the installation command and review the source package before installing it in your own agent environment.
  2. Check the source document for required tools, credentials and supported hosts.
  3. Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/augmnt/webdev-skills --skill writing-commits

Before 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

TypeUse For
featNew user-facing feature
fixBug fix
docsDocumentation only
refactorCode change, no behavior change
testAdding/fixing tests
choreBuild, deps, tooling

Rules

  1. Subject: imperative mood, no period, ≤50 chars
  2. Scope: optional area indicator (auth, api, ui)
  3. 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 15

Anti-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-refresh

Keep branches short-lived. Delete after merge.

Related by task

from this repository

More skills

All skills
augmnt
Community

reviewing-code

Provides structured code review with prioritized feedback. Use when reviewing PRs, analyzing code quality, checking for bugs, or auditing changes. Triggers on "review this", "check this code", PR reviews, or code quality questions.

1h installs
1
GitHub stars
2
Updated
Jan 24
augmnt
Community

organizing-project-files

Provides file organization conventions for React and Next.js projects. Use when creating new files, components, hooks, utilities, or services. Triggers on questions like "where should this go?", "where do I put this?", or when deciding between colocating vs grouping files.

1h installs
1
GitHub stars
2
Updated
Jan 24
augmnt
Community

writing-tests

Guides test creation with practical strategies for unit, integration, and e2e tests. Use when writing tests, deciding what to test, setting up test infrastructure, or discussing coverage. Triggers on "write tests", "should I test", "test coverage", or test file creation.

1h installs
1
GitHub stars
2
Updated
Jan 24
augmnt
Community

using-cli-tools

Enforces CLI tool usage over web dashboards for reproducibility and scriptability. Use when working with Git/GitHub, Supabase, Vercel, Netlify, Cloudflare, AWS, Stripe, Prisma, Docker, or any cloud service. Triggers on deployments, database operations, migrations, PRs, issues, webhooks, or environment management.

1h installs
1
GitHub stars
1
Updated
Jan 24