Enhancement: Two-phase duplicate detection with cooldown period

[Kavirubc]

Problem

Currently, when Simili Bot detects a duplicate issue, it immediately closes or transfers the issue. This can lead to false positives frustrating users who don't have time to contest the decision.

Proposed Solution

Implement a two-phase duplicate detection system:

Phase 1: Detection & Labeling

When a duplicate is detected:

• Add potential-duplicate label to the issue
• Post a comment listing the similar issues found
• Do NOT close or transfer immediately

Phase 2: Delayed Action (after cooldown)

After a configurable cooldown period (e.g., 3 days):

• Check if there's been any human activity (see #ISSUE_NUMBER)
• If no activity: proceed with close/transfer action
• If activity detected: remove potential-duplicate label and skip action

Benefits

• Gives users time to review and contest false positives
• Reduces frustration from immediate incorrect closures
• Maintains automation while adding human oversight
• Improves user trust in the bot

Configuration

Add to .simili.yaml:

duplicate_detection:
  cooldown_days: 3
  labels:
    potential: "potential-duplicate"
    confirmed: "duplicate"

Implementation Notes

• Requires new auto-close command for scheduled workflow
• Should track timestamp when potential-duplicate label is added
• See related issue for human activity detection logic

[gh-simili-bot]

Simili Triage Report

Note

Quality Score: 8.5/10 (Good)
The issue is well-described.

Classification

Category	Value
Labels

Similar Threads

Similarity	Thread	Status
78%	#50 [Reliability]: Implement Exponential Backoff fo...	Open
77%	#43 [0.2.0v][Feature] PR indexing with dedicated co...	Open
77%	#36 Similar Issue	Open

---

_{Generated by Simili Bot}