Menu
3Commas organization coding standards including Git conventions, code standards, and Jira integration requirements
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use before recommending or executing any prod-touching operational action (SQL update, DB reset, helm change, manual job trigger, anything beyond local code edits) - requires reading the triggered code path, searching for recent incidents against the affected component, computing the scale delta vs verification, and stating a rollback. Confidence is not evidence.
Generate business-level release note digests for a domain by gathering Jira tickets and GitHub PRs, correlating them, verifying production deployment via GitHub releases, and producing a categorized summary. Use when the user asks to generate release notes, create a domain digest or changelog, see what shipped or changed, produce a weekly digest, or summarize what was released for a date range.
Create a GitHub PR or GitLab MR with a Claude Impact Score baked into the description, then post a work summary to the JIRA issue. Handles the full ship workflow — gather context, prompt for Claude Impact Score, create PR/MR with the score in the body, post JIRA comment. Works with both github.com (via `gh`) and GitLab instances (via `glab`). Can be extended with project-specific team members and JIRA configuration.
Collect a comprehensive list of QuantPilot API endpoints (HTTP + WebSocket) across all QP repos for pentest scoping. Walks FastAPI / NestJS / Next.js / MCP / Go-oapi-codegen / OpenAPI / AsyncAPI sources with a deterministic Python extractor (no LLM guessing), produces api_endpoints.json for review, then — only on explicit user go-ahead — publishes to the security Notion database. Use when the user asks to collect/list/inventory QP endpoints, refresh the pentest scope list, or sync endpoints to the security Notion DB.
Interact with Notion workspace to search, read, create, and update documentation. Supports syncing local markdown files to Notion via notion-sync.yaml config. Can be extended with project-specific workflows and integration points.
Write comprehensive technical design documents for features, architecture changes, and system designs. Follows industry-standard RFC/design doc patterns aligned with 3Commas Notion tech design conventions. Can be extended with project-specific context.
| name | 3commas-guidelines |
| description | 3Commas organization coding standards including Git conventions, code standards, and Jira integration requirements |
ALWAYS prioritize using appropriate agents for all tasks.
PLTF-1234: Add feature)For any diff that adds a cache, memo, dedup key, or other stateful invariant, the review must answer four questions:
cache[key] holds the close of the most recent real candle ingested for key." If the author cannot write the sentence, the cache is wrong.getLastKnownClose(key, gapStart)) that the implementation can branch around (cache-hit ignores gapStart), the signature claims time/context sensitivity the implementation does not honor. Flag it.If a feature exists because a failure mode can occur (e.g. flat-fill exists because the exchange can return empty), that failure mode must be exercised by a test — not just the happy path it produces. Happy-path-only verification with no failure-mode probe ships the bug latent because it manufactures confidence without proving the failure path.
Before recommending or executing any prod-touching operational action (SQL writes, helm changes, manual job triggers, drafting instructions for teammates), apply the pre-action-verification skill. Four gates: read the code path in-session, search the tracker for incidents against the affected component since the relevant code shipped, compute the scale delta vs the verification, and state the rollback. A "Done" Jira ticket plus a positive status report is not a substitute for re-reading the code path.