Idea: Track recurring findings across runs through resolution

Open
#11 1 comment 0 reactions 0 assignees View on GitHub

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
Tech stack
django, python

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

area: runs idea

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

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from piotrekno1/second-shift

All issues in piotrekno1/second-shift

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.