Protect react-native from AI slop PRs
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 127k
- Forks
- 25.3k
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 4
Description
6 of 151 PRs in the last 2 weeks would have been auto-closed before review (e.g. #56812 Update react-native-devtools-frontend URLs, #56803 fix(cocoapods) Podfile.lock SPEC CHECKSUMS drift for React X).
Install a GitHub Action:
- PR Quality Gate, judges PR quality not authorship, lets competent bots through, blocks lazy humans
- anti-slop, 34 configurable checks, built from maintaining Coolify (120 slop PRs/month)
- agentscan-action, deep author profile analysis, detects automation patterns from account activity
This was partially generated by a clanker. The human that sent me cares about your repo. We just wanna help.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the three linked action proposals, including the referenced action.yml, and review the recent PR examples #56812 and #56803. Compare the proposed checks and installation approaches, then define the repository’s desired behavior and the passing and failing outcomes that would count as done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, react-native
- Domain
- ci-cd, developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100