📦 deps(thirdparty): update snapshots
This commit is contained in:
@@ -0,0 +1,37 @@
|
||||
---
|
||||
name: Bug Report
|
||||
about: Something the skill gets wrong — a missing finding, a false positive, or broken output
|
||||
labels: bug
|
||||
assignees: ''
|
||||
---
|
||||
|
||||
## What happened
|
||||
|
||||
<!-- Describe the incorrect behavior. What did brooks-lint do? What did you expect? -->
|
||||
|
||||
## How to reproduce
|
||||
|
||||
**Review mode:** <!-- PR Review / Architecture Audit / Tech Debt / Test Quality / Health Dashboard -->
|
||||
|
||||
**Input (code snippet or description):**
|
||||
```
|
||||
<!-- paste the code or describe the scenario -->
|
||||
```
|
||||
|
||||
**Brooks-lint output:**
|
||||
```
|
||||
<!-- paste the actual output -->
|
||||
```
|
||||
|
||||
**Expected output:**
|
||||
<!-- Describe what a correct review should have flagged or said differently -->
|
||||
|
||||
## Platform
|
||||
|
||||
- [ ] Claude Code
|
||||
- [ ] Codex CLI
|
||||
- [ ] Gemini CLI
|
||||
|
||||
## Version
|
||||
|
||||
<!-- Paste the brooks-lint version (shown in the README badge, or run `/plugin list` in Claude Code). -->
|
||||
@@ -0,0 +1,35 @@
|
||||
---
|
||||
name: Feature Request
|
||||
about: Suggest a new decay risk, a new review mode, or an improvement to the skill
|
||||
labels: enhancement
|
||||
assignees: ''
|
||||
---
|
||||
|
||||
## What problem does this solve?
|
||||
|
||||
<!-- Describe the gap. What does brooks-lint miss or do poorly that this would fix? -->
|
||||
|
||||
## Proposed change
|
||||
|
||||
<!-- Which file(s) would need to change? Rough idea of what to add/modify. -->
|
||||
|
||||
| File | Change |
|
||||
|------|--------|
|
||||
| `skills/_shared/common.md` | |
|
||||
| `skills/_shared/decay-risks.md` | |
|
||||
| `skills/_shared/test-decay-risks.md` | |
|
||||
| `skills/brooks-review/` | |
|
||||
| `skills/brooks-audit/` | |
|
||||
| `skills/brooks-debt/` | |
|
||||
| `skills/brooks-test/` | |
|
||||
| Other: | |
|
||||
|
||||
## Book citation (if applicable)
|
||||
|
||||
<!-- If this idea comes from one of the six books (or a book not yet covered), cite it here. -->
|
||||
|
||||
## Would you be willing to contribute this?
|
||||
|
||||
- [ ] Yes, I can open a PR
|
||||
- [ ] I'd need guidance
|
||||
- [ ] Just leaving the idea here
|
||||
+28
@@ -0,0 +1,28 @@
|
||||
---
|
||||
name: New Eval Scenario
|
||||
about: Propose a test case for the benchmark suite — no code required
|
||||
labels: enhancement
|
||||
assignees: ''
|
||||
---
|
||||
|
||||
## Scenario
|
||||
|
||||
**Review mode:** <!-- PR Review / Architecture Audit / Tech Debt / Test Quality — Health Dashboard aggregates the other four and has no dedicated eval scenarios -->
|
||||
|
||||
**Decay risk targeted:** <!-- R1 Cognitive Overload / R2 Change Propagation / R3 Knowledge Duplication / R4 Accidental Complexity / R5 Dependency Disorder / R6 Domain Model Distortion / T1-T6 for test risks -->
|
||||
|
||||
## Input
|
||||
|
||||
<!-- Describe the code scenario or paste a snippet. It doesn't need to be a real codebase — a minimal example is fine. -->
|
||||
|
||||
```
|
||||
<!-- code or description -->
|
||||
```
|
||||
|
||||
## Expected finding
|
||||
|
||||
<!-- What should brooks-lint flag here? Describe the symptom, which book/principle it maps to, and the severity (🔴/🟡/🟢). -->
|
||||
|
||||
## Why this matters
|
||||
|
||||
<!-- One sentence: what real-world problem does this scenario represent? -->
|
||||
Reference in New Issue
Block a user