committing-work
Use when creating git commits, staging changes, or writing commit messages. Provides Angular conventional commit format guidelines, atomic commit principles, and strategies for splitting multi-concern changes into logical commits.
What this skill does
# Committing Work
## Overview
Commits follow the Angular conventional commit format: `<type>(<scope>): <description>`. Each commit should be atomic (single purpose) and use imperative mood ("add feature" not "added feature").
## Quick Reference
| Type | Purpose |
|------|---------|
| `feat` | New feature |
| `fix` | Bug fix |
| `docs` | Documentation only |
| `style` | Formatting, whitespace (not CSS) |
| `refactor` | Code change without feature/fix |
| `perf` | Performance improvement |
| `test` | Adding or fixing tests |
| `build` | Build system or dependencies |
| `ci` | CI configuration |
| `chore` | Other (no src/test changes) |
| `revert` | Reverts previous commit |
## Format
```
<type>(<scope>): <description>
[optional body]
[optional footer]
```
- **scope**: Optional, indicates affected module/component
- **description**: Imperative mood, under 72 characters
- **Breaking changes**: Add **!** after type/scope (e.g., **feat!: remove deprecated API**) or include **BREAKING CHANGE:** in footer
## Key Principles
1. **Atomic commits**: One commit = one logical change
2. **Imperative mood**: "add" not "added", "fix" not "fixed"
3. **Concise first line**: Under 72 characters
4. **Focus on why**: Explain the reason, not just the what
5. **Ignore irrelevant changes**: Skip temporary files or unrelated modifications
## When to Split Commits
Split when changes involve:
- **Different concerns**: Unrelated parts of the codebase
- **Different types**: Mixing features, fixes, refactoring
- **Different file patterns**: Source code vs documentation
- **Large scope**: Changes clearer when broken down
## Examples
**Good commit messages:**
- `feat: add user authentication system`
- `fix: resolve memory leak in rendering process`
- `docs: update API documentation with new endpoints`
- `refactor: simplify error handling logic in parser`
- `feat(auth): implement transaction validation`
- `fix!: patch critical security vulnerability in auth flow`
**Split commit sequence:**
1. `feat(types): add new solc version type definitions`
2. `docs: update documentation for new solc versions`
3. `build: update package.json dependencies`
4. `test: add unit tests for new solc version features`
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.