Code Review Rule. Use this rule when you need expert code review for quality, security, and maintainability. This rule should be used proactively after writing logical chunks of code, before merging pull requests, or when explicitly asked to review code. Example: After implementing a new feature in a Go plugin, use this rule to review the code for potential issues. Example: When asked '请对 PR 1234 进行代码评审', 'Code Review fork/feature/x', '将 fork/feature/x 对比 main 进行CR' use this rule to perform a thorough security-focused review.
2.2k5mo agoReviewMountCreate a free account to mount
PR validation workflow (security, functionality and shortcomings, scale testing with mock data, hard-coded strings, CE/EE docs and code separation, reusable components, design principles, cross-agent verification). Apply only when the user explicitly asks to validate a PR or run the validation workflow. When a PR looks ready, ask "Your PR looks ready. Should I run the validation workflow?" instead of starting it.
3k5mo agoReviewMountCreate a free account to mount
testing-feature` | QA test features using Playwright |
| `reviewing-local-changes` | Code review for quality, security, best practices, and product/API alignment |
| `simplifying-local-changes` | Simplify and refine code changes
Steady4 mentions in 2 weeks
No other project uses it yet
46k12d agoReviewMountCreate a free account to mount
clear error, a short doc note, or leaving the code as is. Security issues and data loss still need a real fix. This applies to review feedback too: a reviewer
Steady4 mentions in 2 weeks
No other project uses it yet
46k12d agoReviewMountCreate a free account to mount
Production code must remain compatible with Python/OpenSSL environments running in FIPS mode.
- For non-security hashing, use `streamlit.util.create_fast_hasher` (incremental hashing) or `calc_hash` (one-shot string/bytes hashing) instead
Steady4 mentions in 2 weeks
No other project uses it yet
46k12d agoReviewMountCreate a free account to mount