jprdonnelly/core
1
0
Fork 0
mirror of synced 2025-12-19 18:06:02 -05:00
Code Issues Projects Releases Wiki Activity

Clarify year index batch strategy to filter by date range

Browse Source 
Based on eval feedback: Haiku fetched all security months from 2024+2025
instead of just the 12-month window requested.

- Add explicit "filter by date range first" guidance
- Add common mistake: "Fetching all security months from year indexes"
- Emphasize: "last 12 months" ≠ "all of 2024 + 2025"

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
Rich Lander
2025-12-16 20:35:54 -08:00
parent 831bd0a5e2
commit 4c3e4ebd18
1 changed files with 7 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
release-notes/skills/cve.md
View File

@@ -51,15 +51,16 @@ Best for: **4+ months, full year, or multi-year analysis**
```
llms.json → timeline-index → year index
→ [parallel] batch fetch month indexes where security: true
→ filter _embedded.months[] by date range AND security: true
→ [parallel] batch fetch only those month indexes
```
- Fetch year index to see all months with `security: true`
- Batch fetch all relevant month indexes in one turn
- Fetch year index to see all months
- **Filter by your date range first** (don't fetch all security months blindly)
- Batch fetch only the months you actually need
- 3 turns total regardless of month count
- Much more efficient for broad queries
Use `_embedded.months[]` to identify which months have `security: true`, then batch fetch those month indexes (or their `cve-json` links if you need CVSS vectors/CWE).
**Important:** If query asks for "last 12 months", calculate the date range first (e.g., Dec 2024–Dec 2025), then only fetch security months within that range—not every security month in both years.
### Filtering by Version
@@ -140,6 +141,7 @@ Example:
|---------|----------------|
| Using year index batch for 1-3 month queries | Overkill—use `prev-security` walk instead |
| Using `prev-security` walk for 4+ months | Inefficient—use year index batch with parallel fetches |
| Fetching all security months from year indexes | Filter by date range first—"last 12 months" ≠ "all of 2024 + 2025" |
| Fetching `cve.json` for severity/CVSS | Month index `_embedded.disclosures[]` already has this data |
| Constructing month URLs without checking year index | Always check `_embedded.months[]` for `security: true` first |
| Fabricating intermediate month URLs | Trust `prev-security` links—they skip non-security months automatically |