shahar1 opened a new pull request, #454: URL: https://github.com/apache/airflow-steward/pull/454
## Summary - Adds `slop-detection.md` — a new structural scan step (Step 2.5) that runs after the diff is fetched and before line-by-line review begins. - When two or more hard signals fire (or one hard + three soft), the skill presents a slop report and offers targeted actions instead of spending tokens on a full review. - Inserts Step 2.5 into `review-flow.md` with a two-outcome spec (early-exit vs. note-only). - Adds Golden rule 12 to `SKILL.md` and registers the new file in the detail-files table. ## Motivation PRs that are clearly student class projects, personal experiments, or low-effort AI-generated submissions pushed to upstream repos don't warrant a full line-by-line code review. Detecting them early saves reviewer time and surfaces the right response (contribution-guidelines comment, close+lock, or GitHub report) rather than a regular `REQUEST_CHANGES` review. The signals are deliberately high-threshold to avoid false positives: unrecognised top-level directories, private-fork issue references, fork merge-commit floods, multi-author team projects, and extreme area sprawl. Soft signals alone never trigger early exit. ## Maintainer actions on early exit | Key | Action | |---|---| | `[C]` | Post a contribution-guidelines warning comment (template in `slop-detection.md`) | | `[X]` | Close PR + lock conversation (reason: spam) + show GitHub report link | | `[R]` | Review anyway — resumes normal flow from Step 3 | | `[S]` | Skip this PR this session | All write actions (`[C]`, `[X]`) require explicit maintainer confirmation before executing. The skill never auto-closes or auto-comments. --- ##### Was generative AI tooling used to co-author this PR? - [X] Yes — Claude Code (claude-sonnet-4-6) Generated-by: Claude Code (claude-sonnet-4-6) following [the guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
