<!-- This template is for maintainers to use when creating issues that are suitable for first-time contributors. Each good-first-issue should be scoped to a few hours of work and have a clear "done" definition. --> ## Background <!-- 2–3 sentences explaining what part of ASCEND this touches and why it matters. --> ## What needs to be done <!-- A specific, well-scoped task. Example: "Add a Bandit scanner step to the GitHub Actions workflow at .github/workflows/python.yml, gating the build on high-severity findings." --> ## Files to look at - `path/to/file_1.py` - `path/to/file_2.yml` ## Definition of done - [ ] Code change implemented - [ ] Test coverage added (if applicable) - [ ] Documentation updated (if applicable) - [ ] CI passes ## Helpful pointers <!-- Links to relevant docs, similar PRs, external references. --> --- **Estimated effort:** 1–4 hours **Skills needed:** <!-- e.g. "basic Python," "familiarity with YAML," "no prior knowledge required" -->
Background
What needs to be done
Files to look at
path/to/file_1.pypath/to/file_2.ymlDefinition of done
Helpful pointers
Estimated effort: 1–4 hours
Skills needed: