Category
No public results yet
Break a dependency replacement into reviewable stages with compatibility checks, exit criteria and realistic rollback limits.
No public results yet
Define realistic traffic, workload data, measurements and stopping rules for an authorized performance test.
No public results yet
Find source-visible labeling, semantics and keyboard risks, while separating code findings from checks that require a browser.
No public results yet
Map feature assets, trust boundaries and data flows to concrete threats, existing controls and targeted verification tasks.
No public results yet
Turn an API contract into a small client design that handles retryable failures, deadlines and idempotency deliberately.
No public results yet
Interpret supplied plan evidence and prioritize query or index experiments without inventing costs or speedups.
No public results yet
Check whether keys, constraints and relationships actually enforce the application's stated data rules.
No public results yet
Generate a dialect-specific regular expression with match boundaries, annotated examples and stated limits.
No public results yet
Propose a small readability refactor with explicit invariants, behavior risks and a focused equivalence-check plan.
No public results yet
Trace inputs, branches, outputs and side effects in supplied code, with a worked example and clear limits on what can be inferred.
No public results yet
Turn endpoint notes or implementation excerpts into a clear API reference with parameter tables, examples, error handling, and open questions.
No public results yet
Build focused tests for normal behavior, boundaries, failures, and state changes while matching the project's framework and conventions.
No public results yet
Turn a bug report into ranked hypotheses, a minimal reproduction, and diagnostics that distinguish causes before proposing a fix.
Turns a project idea into a complete scaffold: a summary, build steps, directory structure, the purpose of each file, commented source for every file, a setup script and a README.
fix(auth)!: reject refresh tokens issued before a password change Refresh tokens were validated only against their signature and expiry, so a token minted before a password reset stayed usable for its full thirty-day lifetime. Anyone holding a captured token kept access after the account owner rotated their credentials, which is precisely the scenario a password reset is meant to close. The user row now carries credentials_changed_at, and verifyRefreshToken compares the token's iat claim again
Generates a Conventional Commits message from a diff or a plain description, picking the right type and scope, using imperative mood, and flagging breaking changes correctly.
**Summary** Rate limiting for the public search endpoint moves from a per-process in-memory counter to a shared Redis counter, so the limit now applies across all application instances rather than per instance. **Files Changed** - `src/middleware/rate_limit.py` — replaces the module-level `defaultdict` with a Redis-backed sliding window. - `src/config.py` — adds `REDIS_URL` and `SEARCH_RATE_LIMIT_PER_MINUTE`, both required at startup. - `tests/test_rate_limit.py` — new tests covering the wind
Turns raw git diff output into a structured PR description covering summary, files changed, significant code, reasoning, project impact, a test plan and reviewer notes.
### Overall Assessment The function's intent is immediately obvious, which is a real strength — nobody will misread what it returns. Its two weaknesses are both structural rather than cosmetic: it issues one database round trip per user, and it raises an unhandled exception the first time an id has no matching row. ### Prioritized Recommendations 1. Replace the per-id query with a single `IN` query to eliminate the N+1 pattern. 2. Decide explicitly what should happen when a user id has no row
Reviews a snippet or diff across correctness, security, performance, readability, idiom and error handling, then returns prioritized fixes with before/after code and a rationale for each.