writing-git-commits
Write clean, atomic conventional commits from staged or uncommitted changes. Use when asked to commit, generate commit messages, or clean up git history.
What this skill does
# Writing Git Commits ## Workflow 1. **Inspect** — `diffs --staged` (staged) and `diffs` (unstaged); fallback to `git diff --stat` when raw line stats required2. **Group** — cluster related changes into atomic commits (one logical change per commit) 2. **Order** — commit foundational changes first (deps, config, types), then features, then tests 3. **Write** — craft each message per the format below 4. **Stage & commit** — `git add -p` or `git add <paths>` then `git commit -m "..."` ## Message Format ``` <type>(<scope>): <subject> [optional body] [optional footer] ``` ### Types | Type | When | | ---------- | --------------------------------------- | | `feat` | New feature or capability | | `fix` | Bug fix | | `refactor` | Code change that neither fixes nor adds | | `docs` | Documentation only | | `test` | Adding or updating tests | | `chore` | Build, CI, deps, tooling | | `style` | Formatting, whitespace, semicolons | | `perf` | Performance improvement | ### Rules - **Subject**: imperative mood, lowercase, no period, ≤72 chars - **Scope**: optional, the module/area affected (e.g., `auth`, `pi`, `nix`) - **Body**: wrap at 72 chars, explain _what_ and _why_ (not _how_) - **Footer**: `Closes #123`, `BREAKING CHANGE: ...` - **Atomic**: each commit compiles/passes independently - **No mixed concerns**: don't combine a bugfix with a refactor ### Examples ``` feat(pi): add diff-renderer extension chore: update flake inputs fix(auth): prevent token refresh race condition Tokens were being refreshed concurrently, causing 401s for in-flight requests. Added a mutex around the refresh call. Closes #42 refactor(shell): extract zsh plugin config to module ``` ## Grouping Heuristics - Same file touched for different reasons → separate commits - Multiple files for one feature → single commit - Formatting/whitespace mixed with logic → split them - Dependency updates → own commit (`chore(deps): ...`) - Generated files (lockfiles, schemas) → commit with the change that caused them
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.