brynhild-development

Set up a development environment by creating and activating a Python virtual environment within the project, avoiding system Python. Install dependencies, then run pytest for testing, mypy or pyright for type checking, and ruff for linting to maintain code quality.

Brynhild enforces qualified imports and specific code formatting standards. Use ruff for linting compliance, follow the documented import style conventions, and ensure all code adheres to the project's type-checking requirements before committing.

Run pytest to execute the test suite, then run mypy or pyright for type checking to catch static errors. Both checks must pass before submitting changes. Use ruff to lint your code and ensure it meets formatting standards.

Use the commit-helper workflow to structure and submit commits. This ensures commits follow project conventions, pass all checks, and maintain consistency across the codebase before merging.

Skills are stored and managed in the `.brynhild/skills` directory. Follow the project structure, apply all code conventions, and run the full test and type-checking suite before committing skill additions or edits.

Yes, you must use a project virtual environment and avoid system Python. The project requires an isolated venv to ensure consistent dependencies and prevent environment-related issues during development and testing.