conventional-git
Conventional Commits v1.0.0 branch naming, worktree naming, and commit message standards for GitHub and GitLab projects. Use when creating branches, naming worktrees, writing commits, generating commit messages, reviewing branch conventions, or setting up changelog automation. Apply when your project needs consistent git history, SemVer-driven releases, parseable changelog generation, or automatic issue closing. Trigger when the user asks how to name a worktree, create a git worktree, or organize worktrees alongside branches.
git clone --depth 1 https://github.com/samber/cc-skills /tmp/conventional-git && cp -r /tmp/conventional-git/skills/conventional-git ~/.claude/skills/conventional-gitSKILL.md
# Conventional Commits & Branch Naming Follow Conventional Commits v1.0.0 for both branch names and commit messages — consistent naming lets tools auto-generate changelogs, enforce SemVer bumps, and filter history by concern. ## Branch Naming Format: `<type>/[issue-]<description>` — lowercase, hyphens only, no special chars except `/`. ``` feat/user-authentication feat/42-user-authentication fix/login-race-condition fix/87-login-race-condition docs/api-reference-update refactor/payment-module ``` Prefix with the issue number when one exists — GitHub and GitLab auto-link it and it makes `git log` immediately traceable to the tracker. Keep the description under 50 characters — most git UIs truncate branch names in lists around that length. Match the type to the work you're doing — this is the contract readers use to understand the branch purpose at a glance. NEVER include `worktree` in a branch name — git worktrees are a local checkout mechanism, not a branch concept; the name would leak implementation details into the remote and confuse other contributors. ## Worktree Naming Worktrees are local checkout directories — they never appear in the remote. Place them under `.claude/worktrees/` and name them by replacing the branch `/` separator with `-`. ``` git worktree add .claude/worktrees/feat-user-authentication feat/user-authentication git worktree add .claude/worktrees/fix-87-login-race-condition fix/87-login-race-condition ``` The directory name mirrors the branch name so `git worktree list` stays readable and each worktree is immediately traceable to its branch without inspecting the checkout. Run `git worktree list` before creating a new one — reuse an existing worktree if it already covers the same branch. Keep worktrees scoped to a single branch. Doing unrelated work inside someone else's worktree obscures which changes belong where and makes cleanup error-prone. Remove the worktree once its branch is merged — either after a local merge or after the pull/merge request is closed on the remote. Stale worktrees accumulate and make `git worktree list` unreadable. ```bash git worktree remove .claude/worktrees/feat-user-authentication # branch merged locally git worktree prune # remove refs to already-deleted directories ``` ## Commit Message Format ``` <type>[optional scope]: <description> [optional body] [optional footer(s)] ``` **Types:** | Type | SemVer | When | | ---------- | ------ | ---------------------------- | | `feat` | MINOR | New feature | | `fix` | PATCH | Bug fix | | `docs` | — | Docs only | | `style` | — | Formatting, no logic change | | `refactor` | — | Restructure, no feature/fix | | `perf` | — | Performance improvement | | `test` | — | Add/fix tests | | `build` | — | Build system, deps | | `ci` | — | CI config | | `chore` | — | Anything else (not src/test) | | `revert` | — | Reverts a previous commit | **Rules:** - Subject line ≤ 72 characters — git log and GitHub/GitLab UIs silently truncate longer subjects - Imperative mood: "add" not "added" — reads as an instruction, not a history log - No capital letter, no trailing period — enforces uniform parsing by changelog tools - Body separated by blank line — parsers split header/body at the first blank line - Breaking changes: use `!` after type/scope, or add `BREAKING CHANGE:` footer (triggers MAJOR bump) — body-only descriptions are invisible to changelog tools - `revert` commits SHOULD include `This reverts commit <hash>.` in the body — `git revert` generates this automatically; don't strip it - NEVER add a Claude signature, AI agent attribution, or `Co-authored-by` trailer for Claude or any other AI agent to commits **Examples:** ``` feat(auth): add JWT token refresh ``` ``` fix: prevent race condition on concurrent requests Introduce request ID and reference to latest request. Dismiss responses from stale requests. ``` ``` refactor!: drop support for Go 1.18 BREAKING CHANGE: Go 1.18 no longer supported; uses stdlib APIs from 1.21+ ``` ## Closing Issues via Commit Messages Both GitHub and GitLab detect keywords in commit messages and automatically close the referenced issue when the commit lands on the default branch. Place the reference in the **footer** (preferred — keeps the subject line clean). **Keywords:** `close`, `closes`, `closed`, `fix`, `fixes`, `fixed`, `resolve`, `resolves`, `resolved` — case-insensitive. **GitHub:** ``` fix(auth): prevent token expiry race condition Closes #42 Closes owner/repo#99 ``` - Triggers when merged into the **default branch** (usually `main`) - Cross-repo: `Closes owner/repo#42` - Close multiple: `Closes #42, closes #43` - Works in PR descriptions too **GitLab:** ``` feat: add dark mode support Resolves #101 Closes group/project#42 ``` - Triggers when merged into the **default branch** (configurable per project) - Cross-project: `Closes group/project#42` - Close multiple: `Closes #101, closes #102` - Works in MR descriptions too **Tip:** Pair with the commit type — `fix:` closing a bug issue, `feat:` closing a feature request — keeps the changelog semantically coherent. ## Common Mistakes | Mistake | Fix | | --- | --- | | `feat: Added login page` | `feat: add login page` — imperative, no capital | | `fix: fix bug.` | `fix: fix bug` — no trailing period | | Subject over 72 chars | Shorten; move detail to body | | Breaking change only in body | Add `!` or `BREAKING CHANGE:` footer — tools won't detect body-only | | `feat(adding-auth): ...` | `feat(auth): ...` — scope is a noun, not a verb | | Closes #42 in subject line | Move to footer — keeps subject clean and parseable | ## Best Practices - Align branch type and commit type — `feat/auth-*` branch → `feat(auth):` commits
Comprehensive guide for building Chrome extensions with Manifest V3. Use this skill whenever the user mentions Chrome extension, browser extension, manifest.json, content script, service worker (in extension context), popup, side panel, chrome.runtime, chrome.tabs, chrome.storage, chrome.scripting, background script, MV3, Manifest V3, or any Chrome extension API. Also trigger when the user wants to inject scripts into web pages, communicate between page and background, bypass CSP from a content script, build an RPC layer over chrome messaging, or publish to the Chrome Web Store. Covers both new extension projects and adding features to existing ones. Do NOT use for framework-specific questions.
Design end-of-article CTAs (calls-to-action placed at the bottom of blog posts, newsletters, essays, articles, or any long-form content). Use this skill whenever the user asks to write, design, review, or improve a CTA at the bottom of an article, blog post, or essay; mentions "end-of-post CTA", "bottom of the article", "call-to-action", "signup box", "newsletter CTA", "subscribe block", "what should I put at the bottom", "how do I get readers to subscribe / share / book a call / buy / follow / join / download"; or asks how to convert article readers into subscribers, leads, customers, community members, or supporters. Also trigger when the user wants A/B testing guidance or accessibility review for a CTA block. Covers independent / personal writing, newsletter publications, and brand / content-marketing blogs across any topic — tech, finance, food, climate, design, lifestyle, B2B, B2C. Produces both the copy (content) and the structural / visual design (form), matched to the user's objective and audience.
>
Codifies how someone or a brand writes — prose mechanics (lexicon, syntax, rhythm, structure, signature moves) independent of emotional tone. Output: PROSE.md. Three modes: BUILD a fresh guide from SOUL.md + TONE.md + discovery interview; ADAPT an existing guide to a new channel; AUDIT a corpus for prose patterns before codification. Use when: writing rules for a content factory, codifying ghostwriting voice for multi-writer consistency, defining banned words and sentence-length targets, building a house style guide, reverse-engineering prose from a corpus, porting style across channels. Trigger on: PROSE.md, writing style guide, prose guide, house style, ghostwriter style, writing playbook, brand writing mechanics, signature moves. NOT for: writing actual content (→ linkedin-ghostwriting, technical-article-writer, press-release-writer), removing AI patterns (→ humanizer), tone decisions (→ copywriting-tone-of-voice), hooks (→ copywriting-hooks), CTAs (→ copywriting-cta).
Build a brand tone of voice guide (TONE.md) via discovery, voice definition, and channel modulation. Outputs voice attributes with do's/don'ts, NN/g positioning, tone modulation matrix, lexicon, mechanics, and channel rules — consumed by downstream content skills writing on-brand copy. Covers B2B SaaS, B2C/D2C, NGO, public sector, consulting, industrial, product-led, personal, and volunteering brands; researches uncovered contexts (politics, regulated niches, religious orgs, gaming) on demand. Also adapts an existing TONE.md to a new channel (blog → LinkedIn, web → Twitter/X, in-product UI). Optionally consumes SOUL.md to pre-fill brand identity. Apply when the user wants to create a TONE.md, define brand voice, port voice to a new channel, refresh an outdated voice, or set up a content factory writing across many supports. Not for writing individual posts, articles, emails, or UI strings (→ dedicated writing skills), nor SOUL.md, PROSE.md, DESIGN.md.
CRXJS Chrome extension development — true HMR for popup, options, content scripts, side panels, manifest-driven builds, dynamic content script imports (`?script`, `?script&module`), and `defineManifest` for type-safe manifests. Uses Vite as its build tool. Use when the user mentions CRXJS, crxjs, @crxjs/vite-plugin, 'extension with hot reload', 'HMR for chrome extension', or wants to set up a CRXJS-based Chrome extension project with any framework (React, Vue, Svelte, Solid, Vanilla). Also trigger when the user has an existing CRXJS project and wants to add features, fix HMR issues, or configure content scripts with CRXJS. For general Chrome extension architecture (messaging, CSP, storage, permissions) -> See `samber/cc-skills@chrome-extension` skill.
Deep research skill — broad parallel web searches, multi-source validation, confidence tracking, cited Markdown report. Supports 11 research types: market (TAM/SAM, segments, pricing, trends), domain (industry structure, ecosystem, regulatory landscape), technical (architecture, tools, benchmarks), competitive (competitor teardown, positioning, win/loss), product (feature analysis, reviews, roadmap signals), academic (literature survey, citation networks, key authors), person/org (due diligence on a company or public figure), financial (funding rounds, valuation multiples, revenue signals), legal (IP, patents, litigation, compliance), trend (emerging signals, foresight, scenario mapping), community (ecosystem health, key voices, governance, fragmentation). Use when asked to: 'research <topic>', 'deep dive on X', 'analyze the landscape', 'competitive analysis', 'compare these options', 'who are the players in Z', 'literature review', 'background on Y', 'what papers exist on X', 'product teardown', 'technology evaluation', 'regulatory overview', 'funding landscape', 'what trends are emerging in X', 'patent landscape', 'community health', or any request requiring scanning many sources and producing a cited written analysis. Apply whenever the deliverable is a thorough, sourced report rather than a quick answer. Trigger even when phrased casually: 'look into X', 'what's the deal with Y', 'dig into Z', 'I need to understand the space', 'catch me up on X'.
Produce distinctive, non-generic UI and design applications well, working strategy-first. Identify the project (landing page, SaaS app, dashboard, ecommerce, presentation, docs, portfolio...) and its positioning and personality, commit to brand adjectives, translate into a typography and color system, then apply the craft layer (layout, components and states, motion, iconography, imagery, dark mode and theming, accessibility), avoiding the AI-slop / Claude-esque default. This is both a de-slop and an expert app-design skill. Use this whenever building or styling any web frontend, app, dashboard, landing page, deck, or artifact, or when the user says "make it not look like AI", "de-slopify", "deslop", "less generic", "give it character", "design a UI for X", "design an app", "update DESIGN.md", or complains the output looks like every other AI site. Trigger even when the user just says "build a UI for X" without naming an aesthetic, because the default without this skill is slop.