Results for “kommo”

COCO: Microsoft COCO: Common Objects in Context

KOMODO v1.0 — Momentum Event Consensus. Uses leaderboard_get_momentum_events (real-time threshold crossings) to detect when 2+ quality SM traders cross momentum thresholds on the same asset/direction within 60 minutes. Confirmed by market concentration + volume. Enters with the momentum. Replaces MANTIS v1.0 and SCORPION v1.1 (both used stale position data).

You are an expert in Koa, the minimalist web framework created by the Express team. You help developers build APIs and web services using Koa's async/await middleware stack, context object, and composable architecture — providing a lightweight foundation where you add only what you need through middleware, without bundled routing or templating.

Creates standardized git commits using the Conventional Commits specification by analyzing the diff, staging files, and generating appropriate commit messages.

변경된 파일을 기능별로 그룹화하여 커밋 생성

Crie mensagens de commit seguindo as convenções Sentry. Use ao fazer commit de alterações de código, escrever mensagens de commit ou formatar histórico git. Segue conventional commits com referências de issues específicas do Sentry.

Project commit helper for simulator-ai-plugin. Use instead of the generic commit skill whenever the user says "/commit", "commit", "закоммить", "сделай коммит", or asks to commit changes in this repository.

Ultra-compressed commit message generator. Cuts noise from commit messages while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious. Use when user says "write a commit", "commit message", "generate commit", "/commit", or invokes /caveman-commit. Auto-triggers when staging changes.

Stages and commits changes with quality checks, status review, and a clear message, then shows recent history.

Retrieve deterministic search results, metadata, and full-document Markdown from arXiv, PubMed/PMC, and US policy corpora with daily freshness checks.

Turn a diff or plain description into a conventional-commit message - honest type and scope, a why-focused body, breaking changes flagged, nothing invented.

Build Simulink models that co-simulate with Eclipse SUMO traffic simulator. Use when creating SUMO-Simulink co-simulation, traffic simulation, TraCI connection, vehicle-in-the-loop testing, or ADAS scenario validation with SUMO. Covers Server/Client setup, Reader/Writer/Actor block configuration, random traffic generation, ego vehicle control, and SUMO file creation. Also use when the user mentions SumoInterfaceLibrary, .sumocfg files, or wants to connect Simulink to an external traffic simulator.

Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.

Use when the user wants to set, change, or clear git commit co-authors for pair or mob programming.

Generates ultra-compressed commit messages in Conventional Commits format with a subject line ≤50 characters and a body only when the 'why' isn't obvious.

Kotest — flexible, idiomatic Kotlin testing framework. Multiple specification styles (StringSpec, FunSpec, BehaviorSpec, DescribeSpec, FeatureSpec, FreeSpec), rich matcher library, property-based testing, data-driven tests, coroutine support, KMP-friendly. Drop-in alternative or complement to JUnit. USE WHEN: user mentions "Kotest", "io.kotest", "shouldBe", "StringSpec", "BehaviorSpec", "DescribeSpec", "kotest property testing", "Arb.list", "forAll", "kotest matchers", "kotlin tests" DO NOT USE FOR: JUnit-specific patterns - use junit skill (or framework-specific test skills) DO NOT USE FOR: Flow testing - use `testing/turbine` DO NOT USE FOR: Compose snapshot tests - use `testing/compose-snapshot` DO NOT USE FOR: Mobile E2E - use `testing/maestro`

Turn "what should we pay reps and what number do we give them" into a defensible comp and quota plan. Reconciles a top-down number against a bottom-up build, sets the OTE mix, lays out accelerators, and names the behaviors the plan will drive and the ones it will break. Built for B2B sales leaders, customizable to your motion and your segments. Trigger on "design the comp plan", "set quotas", "what OTE should I pay", "reconcile top-down and bottom-up", "what will this plan actually incentivize", or any comp or quota build.

Escribe mensajes de commit, PRs e issues con tono humano en español rioplatense o técnico en inglés, siguiendo reglas de atomicidad, límite de 300 líneas y verificación previa de tests.