From ai-helper
Performs an in-depth PR review for Apache Flink. It analyzes PR descriptions, references JIRA tickets (FLINK-*), explains changes for users with basic Flink knowledge, and provides structured suggestions (nit, minor, major, critical) with code blocks and a final verdict.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ai-helper:flink-pr-reviewerThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill guides you through an exhaustive, human-like PR review process for Apache Flink. Your review must be as in-depth as possible, examining the changes file-by-file and line-by-line. Take your time to thoroughly understand every single modified line.
This skill guides you through an exhaustive, human-like PR review process for Apache Flink. Your review must be as in-depth as possible, examining the changes file-by-file and line-by-line. Take your time to thoroughly understand every single modified line.
gh pr view or branch comparison).FLINK-XXXXX patterns in the description.web_fetch to read the JIRA ticket at https://issues.apache.org/jira/browse/FLINK-<ID> to understand the "Why" behind the change.read_file or grep_search before making a judgment.[File Path]
```cpp
// Code block showing the context
- old_code
+ new_code
Suggestion: Your detailed explanation and recommended fix. Explain exactly why it is an issue at the line level.
- **Suggestion Types**:
- `nit`: Small stylistic or non-functional improvements.
- `minor`: Minor logic improvements or edge case handling.
- `major`: Significant logic errors, performance issues, or API design concerns.
- `critical`: Severe bugs, data loss risks, or security vulnerabilities.
### 4. Self-Correction & Verification
- **Internal Monologue**: Re-read all generated comments.
- Ask: "Is this a false positive?", "Did I misunderstand the Flink internal API?", "Is this suggestion idiomatic for Flink?".
- Filter out any weak or incorrect suggestions. Ensure you have not missed any files from the PR.
### 5. Final Verdict
- Provide a summary of the exhaustive review.
- State a final verdict: **Approve**, **Request Changes**, or **Comment**.
## Guidelines
- **Exhaustive Scope**: Never summarize your review at a high level. You must detail your findings across the entire PR footprint.
- **Flink Idioms**: Check for proper use of `ConfigOption`, `TypeInformation`, serialization, and thread safety.
- **Testing**: Ensure that corresponding tests are added or updated in the PR.
- **Documentation**: Check if `FLINK.md` or other docs need updates.
- **Patience**: It is acceptable to generate a long response if the PR is large. The user wants depth over brevity.
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub spuru9/ai-helper --plugin ai-helper