commit changes to `node_modules/` or generated code without source changes
## Security Considerations
1. **Input Validation**: Always validate and sanitize user input
2. **Path Traversal**: Validate object keys before storage
Steady2 mentions in 2 weeks
No other project uses it yet
12k4mo agoReviewMountCreate a free account to mount
separately; bundle them in their own PR when possible.
- **`package.json` `resolutions`** — these patch known security advisories. Removing entries reintroduces CVEs; check `yarn npm audit --recursive` before pruning.
## Testing expectations
Steady8 mentions in 2 weeks
No other project uses it yet
12k3y agoReviewMountCreate a free account to mount
WalletFactory` keeps `_authorizeUpgrade` with its other
internals near the file end. Rationale: on these security contracts, adjacency of each override and
its helpers keeps the code auditable and preserves
11k53d agoReviewMountCreate a free account to mount
merge, release notes (incl. reporter thanks), tag `origin/main`, publish, re-cut on failure | `/release` |
| [`security-advisory`](.claude/skills/security-advisory/SKILL.md) | A privately reported vulnerability end to end: the draft card, who owns
11k45d agoReviewMountCreate a free account to mount
meaningful public JSDoc. Preserve documentation URLs/import paths; examples must run with documented environments/dependencies.
## Security and lifecycle correctness
Read and apply [contributor security requirements](.github/CONTRIBUTING.md#security-requirements) for credentials/synthetic fixtures, browser
Steady16 mentions in 2 weeks
No other project uses it yet
11k9d agoReviewMountCreate a free account to mount
them upfront.
This gives you setup, architecture, code map, conventions, workflows,
interfaces, gotchas, and security.
3. If a task needs more detail than L1 provides, follow links to L2 deep
11k3d agoReviewMountCreate a free account to mount
tests that do.
- No speculative edge cases or the same behavior tested across layers.
Security, authorization, data integrity, and tricky state transitions do deserve targeted coverage.
- For bug fixes, prefer
11k19d agoReviewMountCreate a free account to mount
changes with maintainers and flag them clearly in both commit body and PR description.
## Security & Configuration Tips
Never commit secrets—use sample files in `env/` or add new templates when
No other project uses it yet
11k26d agoReviewMountCreate a free account to mount
GitHub Actions workflows:
- **Pin actions to full commit SHA** with a version comment for security and reproducibility:
```yaml
# Good - pinned to SHA with version comment
- uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
11k5mo agoReviewMountCreate a free account to mount
Prefer simple conditionals over nested ternary operators
- Group related code together and separate concerns
### Security
- Add `rel="noopener"` when using `target="_blank"` on links
- Avoid `dangerouslySetInnerHTML` unless absolutely necessary
11k51d agoReviewMountCreate a free account to mount
markdown code block. NEVER include secrets, PII, or proprietary prompt content
## GitHub PR and Security Advisories
- If the user asks you to open a GitHub PR or create a GitHub
11k7mo agoReviewMountCreate a free account to mount
code** (i.e., in the same directory) takes precedence on any conflict.
---
## 6. Security Work
When assisting with security-sensitive changes (transport size limits, TLS configuration,
authentication, serialization bounds, or anything
11k2mo agoReviewMountCreate a free account to mount