Idea: Track recurring findings across runs through resolution
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
Research direction
Start by reading the existing documentation-drift workflow and how runs, reports, and repository findings appear in the dashboard; the issue does not name specific files or tests. Define how findings keep a stable identity, how transitions are verified, and how dismissals, snoozes, and notifications persist across runs. Done means the week-long validation reports new, ongoing, fixed, dismissed, and inconclusive findings accurately without repeating notifications for unchanged findings.
Written by the indexing model from the issue text.
Description
Idea
Give recurring reviews continuity across runs: track findings through resolution and notify users when something meaningfully changes.
Problem
SecondShift records execution status, reports, tool activity, and cost, but its main unit of value is still a run. Users must compare successive reports, remember dismissed findings, and determine which problems are new or fixed.
For example, a documentation review finds five stale instructions on Monday. On Tuesday, some remain, one is fixed, and one is dismissed as incorrect. On Wednesday, a new problem appears. The useful update is “One new issue; three still open; one verified fixed,” with evidence, rather than another independent report.
For recurring work, repeated findings could become notification noise even when the first report was useful. This is a product hypothesis based on the current implementation, not validated user research.
Proposed initial scope
Start with the existing documentation-drift workflow:
- Persist findings with evidence and stable identity across runs.
- Distinguish new, ongoing, resolved, and inconclusive findings. A finding being absent from a later report must not automatically count as fixed; resolution needs verification.
- Let users dismiss or snooze findings and respect those decisions on subsequent runs.
- Notify on meaningful changes while keeping the full report available.
- Surface repository findings needing attention alongside execution failures in the dashboard.
The goal is to make the second and tenth runs more useful than the first, and let users see whether engineering problems actually improved.
Validation
Run the workflow against one repository over a week: introduce a problem, let it recur, dismiss another finding, then fix the original problem. Verify that SecondShift reports each transition accurately, avoids repeated notifications for unchanged findings, and does not infer resolution when a check is incomplete.
Treat this as a focused experiment before generalizing finding tracking to every skill.
- Dominant language
- Python
- Stars
- 1
- Forks
- 1
- Avg merge
- 1h 9m
- Merged PRs (30d)
- 322
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from piotrekno1/second-shift
-
code-review secondshift
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
piotrekno1/second-shift#419 ·
Maintainers usually reply within 1 day
-
area: deployment
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
piotrekno1/second-shift#310 ·
Maintainers usually reply within 1 day
-
code-review secondshift
Difficulty 4/5 3-5 days Newbie friendliness 46/100
piotrekno1/second-shift#421 ·
Maintainers usually reply within 1 day
-
code-review secondshift
Difficulty 4/5 3-5 days Newbie friendliness 56/100
piotrekno1/second-shift#420 ·
Maintainers usually reply within 1 day
-
Fix failed-delivery retries on PostgreSQLPossibly taken @piotrekno1 claimed this today. Opencode-review fix-approved secondshift
Difficulty 3/5 1-2 days Newbie friendliness 35/100
piotrekno1/second-shift#418 ·
Maintainers usually reply within 1 day
All issues in piotrekno1/second-shift
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Maintainers usually reply within 1 day
-
area:cli area:security enhancement priority:medium size:small
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
RonaldHensbergen/composable-data-stack#1338 ·
Maintainers usually reply within 1 day
-
area:stdlib effort:S impact:med platform:linux type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
automated endpoint-dead needs-curation
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
almanac-data/climate-almanac#139 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
UKGovernmentBEIS/inspect_ai#6695 · 1 comment ·
Maintainers usually reply within 1 day