'cycles' 검색 결과

Explore explanations for poorly understood phenomena through repeated hypothesis generation and selection. Compare causal mechanisms, test what happens when components change, and retain distinct candidates with predictions, rival comparisons, and clearly stated unresolved questions.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Developing hypotheses for an unexplained phenomenon
• Comparing competing causal explanations
• Identifying predictions that distinguish theories

Investigate recurring problems by mapping feedback loops, the cycles through which effects influence their causes. Identify underlying structures, match known patterns, and assess where changes could help and what unintended effects they might produce.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating recurring incidents
• Understanding coordination problems as teams grow
• Assessing unintended effects before changing a policy

Plan software projects with guidance on short development cycles called sprints, effort estimates, risk management, and stakeholder updates. Clarify responsibilities, coordinate dependencies, and set realistic goals based on the team's capacity.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Planning sprints around team capacity
• Organizing project risks and mitigation plans
• Clarifying responsibilities across teams

Add Mermaid diagrams to generated wiki pages to explain request flows, state changes, data relationships, and branching logic. Keep diagrams aligned with inspected source code and repair syntax problems in diagrams degraded during earlier runs.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Illustrate requests passing between components
• Show job lifecycles and state transitions
• Document relationships between data entities

Control traffic lights in a running CARLA simulation. Change their color, switch them off, hold a fixed state, adjust phase durations, or restore normal cycling, targeting individual lights, junctions, nearby lights, or the whole map.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Holding every traffic light green
• Setting one junction's lights to red
• Shortening traffic-light cycles

Review development plans with external AI tools, then revise and review them again while actionable concerns remain. Choose reviewers and a cycle limit to work toward a plan with resolved review findings.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Review a development plan before implementation
• Revise plans using feedback from multiple AI reviewers
• Use a local model server to review plans

Review selected files for bugs by reading full source code, callers, and related implementations. Apply detailed checklists and investigate suspected issues, then report evidence, confidence levels, and suggested fixes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Review selected files in a critical code change
• Investigate concerns raised by an initial review
• Check complex state transitions and object lifecycles

Navigate Apache Beam contributions from finding an issue to submitting a pull request, a proposed code change, and responding to reviews. Covers environment setup, tests, formatting, licensing requirements, and closer evaluation of changes to core components.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Prepare a first Apache Beam contribution
• Organize a pull request and its related issue
• Check tests and formatting before submission

Turn plain-language descriptions or Mermaid diagrams into interactive, standalone HTML diagrams of systems, workflows, API exchanges, data flows, and state changes. Validate layouts, explore relationships, switch themes, and export diagrams as images or video.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Explain system components and their relationships
• Visualize workflows and approval steps
• Map API calls and data pipelines

Test REST, gRPC, and WebSocket APIs for weaknesses in authentication, access controls, input handling, and configuration. Provides protocol-specific checks, tool guidance, and detection indicators to help document reproducible findings and severity during authorized assessments.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Check access controls across users and roles
• Review token lifecycles and request limits
• Assess gRPC and WebSocket security

Review Git code changes using the CodeRabbit CLI. Receive a summary of the changes and issues ordered by severity, with affected file paths, practical impact, and concrete suggestions for follow-up fixes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing uncommitted code changes
• Checking changes against a base branch
• Organizing quality and security issues by severity

Run repeated Ouroboros execution and improvement cycles as a background job, starting from a Seed specification or continuing an existing lineage. The loop stops on a quality check pass, convergence, cancellation, or the generation limit, and reports the outcome.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Starting repeated improvement from a Seed specification
• Continuing an existing improvement lineage
• Following meaningful background progress

Plan work across several AI agents by defining task owners, deliverables, dependencies, and acceptance criteria. Choose a finite workflow or repeated improvement cycles, then review results before allowing dependent tasks to proceed.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Divide a project among several AI agents
• Choose between a planned workflow and repeated improvement
• Define acceptance criteria for each deliverable

Manage GitHub issues, synchronize project boards, and plan sprints, short development cycles. Coordinate multiple AI agents to break work into tasks, assign responsibilities, update progress, and produce reports on completion and blockers.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Sorting and prioritizing incoming GitHub issues
• Splitting large issues among AI agents
• Synchronizing task progress with project boards

Draft clear instructions for an agent to keep working toward a measurable goal. It defines the objective, constraints, validation commands, and stopping conditions, and guides setup, monitoring, and troubleshooting for the agent's supported runtime.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Drafting a goal prompt with a measurable stopping condition
• Planning repeated test and fix cycles
• Setting up and monitoring an autonomous run

Drive repeated debugging cycles with the required diagnose skill: establish evidence for a cause, choose one focused fix, and rerun the original validation. Reassess after each change until no credible fix remains or further progress requires user input.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Repeating bug fixes and verification until validation is clean
• Checking performance changes against original measurements
• Investigating regressions after each fix

Guides initial BlueField-4 setup through its BMC, the hardware management controller. Covers OS installation methods, firmware updates, post-install checks, and troubleshooting, with action-specific confirmation and maintenance safeguards for changes that can disrupt or damage the device.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Install an OS on a new BlueField-4 through its BMC
• Choose HTTP Boot, PXE, or Redfish Virtual Media
• Update firmware and verify activation

Measure how quickly a host or DPU CPU installs and deletes DOCA Flow rules. Choose a JSON workload and backend, run repeated benchmarks, and record hardware, software, and execution settings so results can be assessed.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Measure BlueField rule installation rates
• Compare DPDK and DOCA backends
• Investigate differences from published benchmark results

Build and debug the shared foundations of DOCA applications on BlueField or ConnectX hardware. Get guidance on device capabilities, memory buffers, context lifecycles, task completion processing, and separate logging controls for the SDK and application.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Setting up the foundations of a DOCA application
• Investigating tasks that submit but never complete
• Sharing memory buffers across DOCA libraries

Automate Linear tasks via Rube MCP (Composio): issues, projects, cycles, teams, labels. Always search tools first for current schemas.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Golang refactoring — safe, at-scale restructuring of existing Go code: a coverage-adaptive safety net, behavior-preserving transforms (gopls Rename/Extract, `gofmt -r`, `gopatch`), the Fowler catalog mapped to Go, breaking import cycles, and small stacked PRs. Apply when a function or type has grown too large, a code smell blocks a feature, or the user asks to refactor Go code — also for renaming at scale, extracting functions or interfaces, moving code between packages, or planning a multi-step refactor. Target styles owned elsewhere → See `samber/cc-skills-golang@golang-naming` (renames), `samber/cc-skills-golang@golang-project-layout` (splits), `samber/cc-skills-golang@golang-modernize` (idioms), `samber/cc-skills-golang@golang-code-style` (control flow), `samber/cc-skills-golang@golang-design-patterns` (patterns/DI).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Analyze how a private SaaS company's ARR valuation multiple changed across funding rounds, and attribute the compression or expansion to rate cycles and macro selloffs, growth deceleration, narrative shifts (including an AI premium), competition, and investor demand, benchmarked against private-market medians and peers. Use this skill whenever the user asks about valuation compression, ARR multiples, round-to-round valuation or multiple changes, down rounds, or wants to compare a VC-backed software company's funding rounds. Research the rounds rather than answering from memory.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when the user asks to "pick a launch date", "plan the launch window", or "set the embargo and lift time"; produces a candidate-window comparison table (conflict / tailwind / risk per window) built from industry-event cycles and the competitor launch calendar, a launch-week vs rolling-release format call, store-review buffer padding (labeled Estimated), and an embargo window definition (lift moment + timezone) submitted to the launch registry as a candidate. Not for judging the cultural moment itself — use trend-spotter; not for launch-day execution — use launch-day-conductor. 发布择时/发布窗口/竞品日历/禁运期窗口/审核缓冲

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Audit an area of the codebase and propose the smallest structural moves that improve it - untangle boundaries, kill duplication, fix seams, break cycles. Produces a prioritized plan and decision records, not a rewrite. Use when a codebase feels tangled, hard to change, or is becoming a ball of mud, or when asked to improve or refactor architecture.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.