Clarify regression detection guidelines and enhance explanation of regression hints

[amir-yogev-gh]

This pull request clarifies and strengthens the guidance around regression detection in both the triage analysis and assessment documentation. The main focus is on emphasizing the insight provided by regression detection and introducing a clear chronological constraint to avoid false positives.

Regression detection improvements:

• Expanded the explanation of what constitutes a regression, highlighting the value of insight into recurring instability and incomplete fixes in both triage/skills/analyze.md and triage/skills/assess.md.
• Added a chronological constraint: only flag a regression if the resolved bug was created before the open bug, preventing incorrect regression links from newer to older issues .
• Updated the required reason field for regressions to focus on why the previous fix may not have held, what area keeps failing, and whether the root cause was incomplete or reintroduced.

These changes ensure regression detection is more accurate, insightful, and actionable for the team.

Summary by CodeRabbit

• Documentation
  • Added explicit chronological constraint to regression guidance: a resolved issue must be created/resolved before an open issue’s creation to be considered a regression.
  • Strengthened regression explanation requirements to mandate an insight-focused description of what broke and why the prior fix may not have held; unchanged behavior remains for nulling when no plausible match exists.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 13448f7e-1a14-4080-bfa3-bdd9a17cd8ac

📥 Commits

Reviewing files that changed from the base of the PR and between 5a5243d and cf3c543.

📒 Files selected for processing (2)

• triage/skills/analyze.md
• triage/skills/assess.md

✅ Files skipped from review due to trivial changes (1)

• triage/skills/assess.md

🚧 Files skipped from review as they are similar to previous changes (1)

• triage/skills/analyze.md

---

Walkthrough

Two documentation files clarifying regression detection are updated. Both add an explicit chronological constraint for matching resolved→open issues, and the regressionOf.reason field is redefined to require an insight-focused explanation of what broke and why the previous fix may not have held.

Changes

Regression Detection Specification

Layer / File(s)	Summary
Core Regression Rule triage/skills/analyze.md	Step 6 regression-detection guidance now requires a chronological constraint (resolved issue's creation date must precede the open issue's creation date). regressionOf.reason is redefined to be an insight-focused explanation of what broke again and why the prior fix may not have held. Example JSON and field bullets updated.
Guidance Reinforcement triage/skills/assess.md	Regression-hint section clarified to require that the resolved bug's resolution date occurs before the open bug's creation date for a regression relationship to be flagged.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The PR title clearly and concisely summarizes the main changes: clarifying regression detection guidelines and enhancing regression hint explanations in the triage documentation.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

• Generate code and open pull requests
• Plan features and break down work
• Investigate incidents and troubleshoot customer tickets together
• Automate recurring tasks and respond to alerts with triggers
• Summarize progress and report instantly

Built for teams:

• Shared memory across your entire org—no repeating context
• Per-thread sandboxes to safely plan and execute work
• Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Review rate limit: 0/1 reviews remaining, refill in 60 minutes.}

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[adalton]

Overall the chronological constraint is a solid addition — without it, the agent could incorrectly link an older unresolved bug as a "regression" of something filed and resolved after it. That's a real failure mode worth preventing. A few issues below.