Skip to content

Add evaluation results summary, trigger evaluation data, and new scripts for PR review#1

Merged
miroslavpojer merged 6 commits into
masterfrom
chore/repo-setup
May 20, 2026
Merged

Add evaluation results summary, trigger evaluation data, and new scripts for PR review#1
miroslavpojer merged 6 commits into
masterfrom
chore/repo-setup

Conversation

@miroslavpojer
Copy link
Copy Markdown
Contributor

@miroslavpojer miroslavpojer commented May 18, 2026

Release Notes:

  • Create initial repo setup.

…pts for PR review

- Created `results-summary.md` to document evaluation results for the pr-review skill, detailing iterations, fixes, and overall trajectory.
- Introduced `trigger-eval.json` containing queries for evaluating trigger conditions, including both should-trigger and should-not-trigger scenarios.
- Added `output-template.md` for standardized PR review output examples, outlining formatting rules and section classifications.
- Developed `security-antipatterns.md` as a reference for identifying security issues during PR reviews.
- Implemented `classify_sections.py` to classify changed files into relevant PR review sections based on defined rules.
- Created `fetch_pr.sh` script to fetch PR details and changed files using the GitHub CLI, facilitating integration with the classification script.
Comment thread .github/workflows/check_pr_release_notes.yml Outdated
Comment thread .github/CODEOWNERS Outdated
Apply only the sections relevant to the files touched by the PR.
Output findings grouped as: Blocker / Important / Nit.

### Skill-specific checks — apply when any `SKILL.md` is modified
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe the pr-reviewer can also include skill review capability & thus this could be removed completely? It would also mean that we don'thave to copy paste this text, just refer to your pr-review skill (skill for now but I think that its scope goes way beyond what skill is)

Copy link
Copy Markdown
Contributor Author

@miroslavpojer miroslavpojer May 20, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree. It can be done in next PR when pr-review will be introduced then we can mentions it here instead of current text.

Comment thread docs/troubleshooting.md Outdated
Comment thread README.md Outdated
…ion in workflow, and clarify troubleshooting documentation
@miroslavpojer miroslavpojer requested a review from lsulak May 20, 2026 12:06
@miroslavpojer miroslavpojer merged commit 9ada7d8 into master May 20, 2026
1 check passed
@miroslavpojer miroslavpojer deleted the chore/repo-setup branch May 20, 2026 13:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants