Skip to content

add workflow for claude script trigger #12

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
berekmerilorand wants to merge 4 commits into
base: master
Choose a base branch
from
Open

add workflow for claude script trigger #12

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
cad8027
add workflow for claude script trigger
berekmerilorand Feb 17, 2026
c849f32
push a fix
berekmerilorand Feb 17, 2026
c8fadb8
debug
berekmerilorand Feb 17, 2026
83db9ce
script updates
berekmerilorand Feb 18, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
52 changes: 52 additions & 0 deletions .github/scripts/CLAUDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,52 @@
# PR Review Guidelines

This document provides guidelines for automated PR reviews using Claude.

## What to Review

### Critical Issues (Always Comment)
- **Bugs and Logic Errors**: Incorrect logic, off-by-one errors, wrong operators
- **Security Issues**: SQL injection, XSS vulnerabilities, unsafe deserialization
- **Missing Error Handling**: Unhandled exceptions, missing edge cases
- **Breaking Changes**: API changes that break existing functionality
- **Test Coverage**: Missing tests for new functionality or bug fixes

### Important Issues (Comment if Significant)
- **Performance Problems**: O(n²) algorithms where O(n) is possible, unnecessary loops
- **Resource Leaks**: Unclosed files, connections, or database cursors
- **Type Safety**: Missing or incorrect type hints in Python
- **Edge Cases**: Division by zero, empty lists, null/None values

### Code Quality (Comment if Egregious)
- **Duplicate Code**: Large blocks of repeated logic
- **Overly Complex Code**: Functions doing too many things, deep nesting
- **Misleading Names**: Variables or functions with confusing names

## What NOT to Review

- **Formatting**: Black handles this automatically
- **Import Order**: Not critical unless it causes issues
- **Minor Style**: Personal preferences about code style
- **Positive Feedback**: Keep reviews focused on improvements only
- **Code Not Changed**: Only review code modified in the PR

## Project-Specific Guidelines

### Python Code
- All functions must have type hints
- Use pytest for all tests
- Follow PEP 8 (enforced by Black)
- Document complex logic with comments

### Testing
- Tests should be in the `specs/` directory
- Test file names must start with `test_`
- Each function should have corresponding tests
- Test for edge cases: empty inputs, null values, division by zero, etc.

## Review Tone
- Be direct and clear about issues
- Focus on **what** is wrong and **why** it matters
- Suggest **how** to fix it when appropriate
- Avoid praise or positive feedback (keep reviews actionable)
- Be pragmatic: only comment on things that truly matter
Loading
Loading