[supercell02]

Summary

Add .editorconfig and .pre-commit-config.yaml to improve developer experience and reduce friction when contributing. These files surface existing code-style decisions (already enforced in CI) to editors and Git hooks, so contributors catch style issues before pushing.

Changes

• .editorconfig: Enforces UTF-8 encoding, LF line endings, final newlines, trailing whitespace cleanup, 4-space indentation for Python (100-char max line length), and 2-space indentation for YAML files
• .pre-commit-config.yaml: Pre-commit hooks for ruff check --fix and ruff format, pinned to v0.16.2 (matching uv.lock)
• CONTRIBUTING.md: Added optional pre-commit setup section with installation and usage instructions

Why This Matters

Pre-v1 contributors often forget to run the manual quality gate (ruff check --fix, ruff format, ty check), leading to style failures in CI. Non-Python files (YAML, Markdown) currently have no convention despite CI checking Markdown. This PR:

• Moves style enforcement earlier (editor + commit time) without breaking existing workflows
• Keeps CI as the source of truth; pre-commit hooks are optional
• Mirrors all existing pyproject.toml style rules (line-length = 100, target-version = "py311")
• Makes onboarding smoother for new contributors

Validation

# All existing files already comply with the new configs
$ uv run ruff check --fix
All checks passed!

$ uv run ruff format
83 files left unchanged

# No diff means configs match CI enforcement
$ git status
nothing to commit, working tree clean

Tested on: Python 3.11, uv 0.4+

Notes for Reviewers

• Configs are intentionally minimal and reference existing decisions in pyproject.toml
• .editorconfig preserves trailing spaces in Markdown (used for line breaks in some contexts)
• Pre-commit installation is documented as optional; CI remains the authoritative gate
• No behavior changes; this is purely developer experience infrastructure

[github-actions]

👋 Hi @supercell02 — thank you so much for your first contribution to HFlow!

A maintainer will review your pull request as soon as possible. In the meantime:

• ⭐ Star the repo: https://github.com/Hebbian-Robotics/hflow
• 📖 Check CONTRIBUTING.md for the validation commands CI will run
• 📣 Share the project with your network

We are excited to have you here and appreciate your help making the project better! 🙌

[Copilot]

Pull request overview

Adds editor and Git-hook configuration to surface existing style/formatting decisions earlier in the contribution workflow, aiming to reduce CI-only style failures and improve contributor ergonomics.

Changes:

• Adds a repository .editorconfig to standardize encoding, line endings, whitespace trimming, and indentation (Python/YAML), with a Markdown exception for trailing spaces.
• Adds a .pre-commit-config.yaml wiring up ruff and ruff-format hooks pinned to v0.16.2.
• Updates CONTRIBUTING.md with an optional pre-commit setup section.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.

File	Description
CONTRIBUTING.md	Documents optional pre-commit usage for running the same Ruff gates locally.
.pre-commit-config.yaml	Introduces pre-commit hooks for Ruff linting/fixing and formatting.
.editorconfig	Establishes editor-enforced whitespace/indentation conventions aligned with existing Python style rules.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[kstonekuan]

Thanks @supercell02! Validated locally: config parses, uvx pre-commit run --all-files passes clean on the tree, and the ruff pin matches uv.lock. I pushed one cleanup commit to your branch: stripped UTF-8 BOMs and double-spacing from the two config files, switched to the current ruff-check hook id, and changed the install instruction to uvx pre-commit (pre-commit is not a project dependency, so uv run pre-commit would fail). Merging.