updated issue templates; added PR template

Author: markleader

.github/ISSUE_TEMPLATE/bug_report.md

@@ -1,32 +1,29 @@
 ---
 name: Bug report
-about: Create a report to help us improve
+about: Report a problem to help us improve
 title: "[bug]"
 labels: bug
 assignees: markleader
-
 ---
 
-**Describe the bug**
-A clear and concise description of what the bug is.
-
-- Interface(s) affected: [e.g. Fortran, C, legacy, Python]
-
-- Is this an issue with backwards-compatibility using the legacy interface? If so, paste the the `.inp` problem file, and the relevant output for inspection.
+**Summary**
+A clear, concise description of the bug.
 
-**To Reproduce**
-Steps to reproduce the behavior:
+**Reproduction**
+- Interface: [Fortran | C | Python | legacy]
+- Minimal input / steps (attach .inp if relevant):
+- Command or API call used:
 
 **Expected behavior**
-A clear and concise description of what you expected to happen.
+What you expected to happen.
 
-**Screenshots**
-If applicable, add screenshots to help explain your problem.
+**Actual behavior**
+What happened (include key error messages/output).
 
-**Build architecture (please complete the following information):**
- - OS: [e.g. Mac OS, Windows]
- - Fortran compiler [e.g. gfortran, ifort]
- - Version [e.g. 3.0.0]
+**Environment**
+- OS:
+- CEA version/commit:
+- Compiler or Python version (if relevant):
 
 **Additional context**
-Add any other context about the problem here.
+Anything else helpful (optional).

.github/ISSUE_TEMPLATE/feature_request.md

@@ -1,17 +1,16 @@
 ---
 name: Feature request
-about: Suggest an idea for this project
+about: Suggest an improvement
 title: "[feature]"
 labels: enhancement
 assignees: ''
-
 ---
 
-**Is your feature request related to a problem? Please describe.**
-A clear and concise description of what the problem is. Ex. It is difficult to [...]
+**Problem / use case**
+What’s hard or missing today?
 
-**Describe the solution you'd like**
-A clear and concise description of what you want to happen.
+**Proposed solution**
+What would you like to see?
 
 **Additional context**
-Add any other context or screenshots about the feature request here.
+Examples, references, or alternatives (optional).

.github/pull_request_template.md

@@ -0,0 +1,10 @@
+## Summary
+
+## Changes
+
+## Testing
+- Not run (explain why)
+
+## Compatibility / Numerical behavior
+- [ ] No expected changes to numerical results
+- [ ] Expected changes (explain and provide validation)

CONTRIBUTING.md

@@ -82,6 +82,9 @@ Large refactors or algorithmic changes should be discussed before implementation
    - Why the change is needed
    - Whether numerical behavior is expected to change
    This helps avoid duplicated effort and ensures alignment.
+   Use the issue templates for bug reports and feature requests:
+   - `.github/ISSUE_TEMPLATE/bug_report.md`
+   - `.github/ISSUE_TEMPLATE/feature_request.md`
 
 2. **Make Small, Focused Changes**
    Each pull request should ideally address one concern:
@@ -250,6 +253,9 @@ Your PR description should include:
 - Impacted components
 - Whether numerical behavior changes (yes/no)
 
+The PR template provides a concise checklist:
+- `.github/pull_request_template.md`
+
 ## What Not to Change
 
 Please do not: