chore: update references to black

Author: KowalskiThomas

.claude/CLAUDE.md

@@ -23,7 +23,7 @@ This project has custom skills that provide specialized workflows. **Always chec
 **Use whenever:** Formatting code, validating style/types/security, or before committing changes.
 
 **Purpose:** Runs targeted linting and code quality checks using `hatch run lint:*`:
-- Formats code with Black and Ruff auto-fixes
+- Formats code with `ruff check` and `ruff format`
 - Validates style, types, and security
 - Checks spelling and documentation
 - Validates test infrastructure (suitespec, riotfile, etc.)

.claude/skills/lint/SKILL.md

@@ -48,7 +48,7 @@ hatch run lint:typing -- path/to/file.py
 ### Code Formatting
 
 #### `fmt` - Format code (recommended for most edits)
-Formats and validates code style using Black and Ruff.
+Formats and validates code style using Ruff.
 
 **Usage:**
 ```bash
@@ -63,7 +63,7 @@ hatch run lint:fmt -- ddtrace/contrib/flask/
 ```
 
 **What it does:**
-1. Runs Black formatter
+1. Runs the Ruff formatter
 2. Runs Ruff with --fix to auto-fix issues
 3. Re-validates with style checks
 
@@ -94,20 +94,21 @@ hatch run lint:style -- ddtrace/
 ```
 
 **What it validates:**
-- Black formatting
+- Ruff formatting
 - Ruff linting rules
 - Cython linting
 - C code formatting
 - CMake formatting
 
 **When to use:** To verify style compliance before committing without auto-fixes.
 
-#### `black_check` - Check Black formatting
-Validates Python code formatting with Black (no auto-fix).
+#### `format_check` - Check formatting
+
+Validates Python code formatting with `ruff format` (no auto-fix).
 
 **Usage:**
 ```bash
-hatch run lint:black_check -- ddtrace/tracer.py
+hatch run lint:format_check -- ddtrace/tracer.py
 ```
 
 **When to use:** Quick check of Python formatting before committing.

docs/contributing.rst

@@ -35,7 +35,7 @@ suite passes.
 Within a few business days, one of the maintainers will respond with a code review. The review will
 primarily focus on idiomatic Python usage, efficiency, testing, and adherence to the versioning policy.
 Correctness and code style are automatically checked in continuous integration, with style linting managed by
-various tools including Flake8, Black, and MyPy. This means that code reviews don't need to worry about style
+various tools including Flake8, Ruff, and MyPy. This means that code reviews don't need to worry about style
 and can focus on substance.
 
 Pull Request Requirements

hatch.toml

@@ -25,8 +25,8 @@ dependencies = [
 ]
 
 [envs.lint.scripts]
-black_check = [
-    "ruff format {args:.}",
+format_check = [
+    "ruff format --check {args:.}",
 ]
 cmakeformat_check = [
     "bash scripts/cmake-format.sh"
@@ -35,7 +35,7 @@ cformat_check = [
     "bash scripts/cformat.sh"
 ]
 style = [
-    "black_check",
+    "format_check",
     "ruff check {args:.}",
     "cython-lint {args:.}",
     "cformat_check",

hooks/scripts/run-black.sh renamed to hooks/scripts/run-python-format.sh

@@ -1,7 +1,8 @@
 #!/bin/sh
+
 staged_files=$(git diff --staged --name-only HEAD --diff-filter=ACMR | grep -E '\.py$')
 if [ -n "$staged_files" ]; then
-    hatch -v run lint:black_check $staged_files
+    hatch -v run lint:format_check $staged_files
 else
     echo 'hatch style check skipped: No Python files were found in `git diff --staged`'
 fi