「conflicts」の検索結果

Deploy ML models with FastAPI, Docker, Kubernetes. Use for serving predictions, containerization, monitoring, drift detection, or encountering latency issues, health check failures, version conflicts.

日本語の概要は準備中です。原文の説明を表示しています。

Generate, refine, compare, and when needed validate distinctive names for startups, AI products, developer tools, protocols, open-source projects, apps, product families, local businesses, services, companies, nonprofits, and other organizations. Use when asked to name or rename a business, brand, product, venture, shop, studio, or organization; derive a name from an existing project or concept; create a company and product naming system; compare candidates; or check company, domain, package, repository, marketplace, or trademark conflicts. Default to a fast no-browse creative pass; use current validation when the user requests availability or research, or is choosing a final name. Do not claim legal clearance, purchase domains, or present stale or unverified availability as fact.

日本語の概要は準備中です。原文の説明を表示しています。

Use when asked to babysit or watch a PR, when watching an open pull request, after opening or pushing to a PR, or when asked to monitor CI, review comments, merge conflicts, whether a PR is ready to merge, or to trigger a re-review.

日本語の概要は準備中です。原文の説明を表示しています。

Think and work like an expert Automotive Engineer. Use when a task calls for Automotive Engineer judgment. Reasons from vehicle-level requirements, regulatory limits, energy/exergy budgets, and distribution-based durability through DFMEA/DVP&R, DoE calibration (INCA, CANape, HIL), Pacejka tire and multibody models, rainflow fatigue, and source-path NVH analysis while treating undocumented build-level and cal-ID deltas, unmet emissions preconditioning and OBD readiness, ADAS sensor misalignment, and cross-domain torque-arbitration conflicts as first-class failure modes.

日本語の概要は準備中です。原文の説明を表示しています。

Use when you need to resolve an in-progress git merge/rebase conflict.

日本語の概要は準備中です。原文の説明を表示しています。

Analyze indexed codebases via graph database (neug) and vector index (zvec). Covers call graphs, dependencies, dead code, hotspots, module coupling, architecture reports, semantic search, impact analysis, bug root cause from GitHub issues, class diagrams (UML), and PR review (risk scoring, conflict detection, auto-merge candidates, labeling). Also covers creating, inspecting, and repairing a CodeScope index. Use for: code structure, who calls what, why something changed, similar functions, module boundaries, bug tracing, class relationships, PR risk/conflicts, or any question benefiting from a code knowledge graph. Applies when a `.codegraph` index exists in the workspace, or when the user wants to create one.

日本語の概要は準備中です。原文の説明を表示しています。

Git is deceptively simple to learn and incredibly hard to master. The difference between a team that ships and a team that fights merge conflicts all day comes down to workflow discipline. Your git history is documentation - make it tell a story future you can understand. This skill covers branching strategies (trunk-based, gitflow, GitHub flow), commit hygiene, merge vs rebase, conflict resolution, and the commands you actually need. Key insight: most git disasters come from not understanding what you're about to do. 2025 lesson: Trunk-based development with short-lived branches has won. Long-lived feature branches are a code smell. If a branch lives more than a few days, something is wrong with your architecture or process. Use when "git workflow, branching strategy, git merge, git rebase, merge conflict, git commit, trunk-based, gitflow, git history, git revert, git reset, git, version-control, workflow, branching, commits, merge, rebase, collaboration" mentioned.

日本語の概要は準備中です。原文の説明を表示しています。

Founders face unique challenges in how they work. Maker vs manager schedule conflicts. Default alive vs dead math. Time and money slowly leaking away. Effective founders develop systems for navigating these challenges. This skill synthesizes PG's essays on founder productivity and decision-making into an operating system for founder effectiveness. Use when "keywords, contexts, " mentioned.

日本語の概要は準備中です。原文の説明を表示しています。

Audit the vault for structural issues: unresolved wikilinks, orphan notes, dead-end notes, and Obsidian sync conflicts. Optional --fix flags create stubs or surface fixable issues.

日本語の概要は準備中です。原文の説明を表示しています。

Cross-repository dependency audit. Scans package manifests for outdated packages, security advisories, version conflicts, and license issues. Produces a prioritized update plan. Supports Node.js, Python, Rust, and Go projects.

日本語の概要は準備中です。原文の説明を表示しています。

Provide safe git commands for common tasks. Use when a junior developer needs help with branching, commits, or resolving simple conflicts.

日本語の概要は準備中です。原文の説明を表示しています。

Land a PR by monitoring conflicts, resolving them, waiting for checks, and squash-merging when green; use when asked to land, merge, or shepherd a PR to completion.

日本語の概要は準備中です。原文の説明を表示しています。

Runs a long swarm of hundreds to thousands of cheap headless coding workers that drive a large failing-test backlog to green. Failures are clustered by signature, each worker fixes one cluster in its own git worktree, a serial no-regression merge gate lands the fixes, the loop resumes across restarts for hours, and it federates across sibling sessions over git branches when one container's CPU is not enough. Use for "fix these thousands of failing tests with a Haiku swarm", "drive the test suite to green with hundreds of agents", "build this compiler or interpreter against a conformance suite", "launch, relaunch or check in on the swarm loop", "the swarm is stuck, idle or rejecting everything", "parallel agents fixing tests keep hitting merge conflicts and regressions", "add sibling containers to the swarm", or "compare models on the tail the swarm could not fix". Ships the harness, a per-project TOML config, a fake-worker selftest, check-in signals and the 2026-10-12 haiku-cc failure catalogue.

日本語の概要は準備中です。原文の説明を表示しています。

Use when you need to resolve an in-progress git merge/rebase conflict.

日本語の概要は準備中です。原文の説明を表示しています。

Computes a numeric or categorical answer to a quantitative data-science question by cleaning and analyzing local data files (CSV, Excel, TSV, and scientific formats .npz/.fits/.h5) with pandas, numpy, and scipy. Use whenever a task ships its own dataset (in whatever local directory it provides) and asks you to derive a value via statistical, geospatial, temporal, ratio, percentage, growth-rate, correlation, signal-processing, orbital, or forecasting analysis. Spans domains including archeology (demographics, paleoclimate proxies, radiocarbon dating, historical conflicts); biomedical/bioinformatics (tumor histology, genes, proteins, peptides, genomic variants); environmental (water quality, bacterial/Enterococcus exceedance, rainfall correlations, environmental justice); legal/consumer (fraud, identity theft, consumer complaints by state/metro); wildfire (incidents, causes, suppression costs, acres burned, fatalities, geospatial intersections); and astronomy/heliophysics/space weather (satellite telemetry TLE/Swarm/SP3, indices OMNI/GOES, solar activity, atmospheric density, orbital mechanics, forecasting).

日本語の概要は準備中です。原文の説明を表示しています。

Check product and brand names for conflicts across trademarks, domains, social handles, and package registries. Returns a risk level and Proceed/Modify/Abandon verdict. Don't use for name brainstorming, logo design, or trademark filings.

日本語の概要は準備中です。原文の説明を表示しています。

Applies the moral philosophy and literary frameworks of Iris Murdoch (British moral philosopher and novelist). Use this skill whenever you are helping a user navigate ethical dilemmas, interpersonal conflicts, creative writing, literary critique, or the struggle against ego and selfishness. Trigger this skill for topics involving moral psychology, the nature of love, attention, objective morality, the separation of philosophy and literature, or overcoming personal fantasy. Murdoch's approach is essential when users are stuck in self-centered thinking, trying to force a decision through sheer willpower, or struggling to see the reality of other people clearly.

日本語の概要は準備中です。原文の説明を表示しています。

Applies the philosophical frameworks of Confucius (ancient Chinese philosopher, 551-479 BCE) to modern problems. Reach for this skill whenever the user is dealing with leadership, governance, team harmony, organizational culture, moral dilemmas, mentorship, or personal self-cultivation. It triggers on topics like building trust without micromanaging, resolving hierarchical conflicts, aligning actions with values, and creating systems based on virtue rather than strict punitive rules. Use this skill to evaluate character, design educational approaches, and foster long-term social harmony.

日本語の概要は準備中です。原文の説明を表示しています。

Resolve stale facts and authority conflicts.

日本語の概要は準備中です。原文の説明を表示しています。

Grounds version-sensitive engineering decisions in authoritative current sources by detecting the installed stack, retrieving official documentation or source, reconciling conflicts, and recording citations and confidence. Use for framework APIs, dependency behavior, standards, compatibility, migrations, or technical recommendations that may have changed. Not for stable project-local logic or broad product discovery.

日本語の概要は準備中です。原文の説明を表示しています。

Holistic cross-GDD consistency and game design review. Reads all system GDDs simultaneously and checks for contradictions between them, stale references, ownership conflicts, formula incompatibilities, and game design theory violations (dominant strategies, economic imbalance, cognitive overload, pillar drift). Run after all MVP GDDs are written, before architecture begins.

日本語の概要は準備中です。原文の説明を表示しています。

Validates completeness and consistency of the project architecture against all GDDs. Builds a traceability matrix mapping every GDD technical requirement to ADRs, identifies coverage gaps, detects cross-ADR conflicts, verifies engine compatibility consistency across all decisions, and produces a PASS/CONCERNS/FAIL verdict. The architecture equivalent of /design-review.

日本語の概要は準備中です。原文の説明を表示しています。

Scan a repo for mixed ADRs, PRDs, SPECs, and DOCs and bootstrap or merge the full .planning/ setup from them. Classifies each doc in parallel, synthesizes a consolidated context with a conflicts report, and routes to new-project or merge-milestone depending on whether .planning/ already exists.

日本語の概要は準備中です。原文の説明を表示しています。

Harmonize multiple Blender skills into a coherent pipeline with clear activation precedence, handoff artifacts, dependency gates, and conflict-resolution rules. Use when a Blender task spans several skills, when reference-locked work conflicts with generic production workflow, after adding/updating skills, or when repeated failures indicate skill interference or missing inter/intra-play.

日本語の概要は準備中です。原文の説明を表示しています。