---
name: Good first issue (maintainer use)
about: Template for creating well-scoped good first issues. Use this when preparing issues for new contributors.
title: "[good first issue] "
labels: good first issue
assignees: ''
---

<!--
  Maintainer guide: use this template to create issues that are genuinely
  approachable for first-time contributors. Fill in every section — the more
  context you provide, the more likely someone starts.
-->

## What needs to change

<!-- One sentence describing the problem or improvement. -->

## Why this matters

<!-- Connect it to signal quality, explainability, false-alarm reduction, or onboarding. -->

## Affected files

<!-- List the specific files or directories involved. -->

- `path/to/file.py`

## Definition of done

<!-- Clear, checkable acceptance criteria. -->

- [ ] …
- [ ] `make test-fast` passes
- [ ] PR follows [CONTRIBUTING.md](../../CONTRIBUTING.md)

## Difficulty estimate

<!-- Pick one: 15 min / 30 min / 1 hour / 2+ hours -->

**Estimated time:** ~30 min

## Hints and context

<!-- Any pointers that help a newcomer get started: relevant functions, test patterns, docs sections. -->

## Maintainer note

Happy to guide — comment here if you'd like to pick this up and I'll help you scope the approach.
