spatie-version-control
Apply Spatie's version control conventions when creating commits, branches, pull requests, or managing Git repositories; use for naming repos, writing commit messages, choosing branch strategies, and merging code.
What this skill does
# Spatie Version Control Guidelines ## Overview Apply Spatie's Git and version control conventions for consistent repository management. ## When to Activate - Activate this skill when creating commits, branches, or pull requests. - Activate this skill when naming new repositories. - Activate this skill when deciding on branching or merging strategies. ## Scope - In scope: Git operations, repository naming, branch naming, commit messages, merge strategies. - Out of scope: Code style, deployment pipelines, CI/CD configuration. ## Repository Naming ### Site source code Use the main domain name in lowercase, without `www`: - Good: `spatie.be` - Bad: `https://www.spatie.be`, `www.spatie.be`, `Spatie.be` ### Subdomains Include the subdomain in the repo name: - Good: `guidelines.spatie.be` - Bad: `spatie.be-guidelines` ### Packages and other projects Use kebab-case: - Good: `laravel-backup`, `spoon` - Bad: `LaravelBackup`, `Spoon` ## Branches ### Initial development - Maintain `main` and `develop` branches. - Commit through `develop`, not directly to `main`. - Feature branches are optional; if used, branch from `develop`. ### Live projects - Delete the `develop` branch. - All commits to `main` must come through feature branches. - Prefer squashing commits on merge. ### Branch naming - Use lowercase letters and hyphens only. - Good: `feature-mailchimp`, `fix-deliverycosts`, `updates-june-2016` - Bad: `feature/mailchimp`, `random-things`, `develop` ## Commits ### Message format - Always use **present tense**. - Good: `Update deps`, `Fix vat calculation in delivery costs` - Bad: `wip`, `commit`, `a lot`, `solid` ### Granularity - Prefer small, focused commits over large ones. - Use `git add -p` for interactive staging to create granular commits. ## Merging - Rebase regularly to reduce merge conflicts. - For deploying feature branches: use `git merge <branch> --squash`. - If push is denied: use `git rebase` (not merge). ## Pull Requests - Optional but useful for peer review, merge validation, and historical reference. --- Source: https://spatie.be/guidelines/version-control
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.