「issue」の検索結果

Manage the kanban board. List, read, and close GitHub issues.

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

Implement regenerative recovery using triage, scaffolding, and progressive rebuild. Covers damage assessment, wound classification, emergency stabilization, scar tissue management, and resilience strengthening for systems that have sustained structural damage. Use when a system has suffered an incident needing structured recovery, when a failed transformation left the system in a damaged intermediate state, when accumulated technical debt has caused partial failure, or when a system is functional but degraded and the degradation is worsening.

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

Manage R package dependencies using renv for reproducible environments. Covers initialization, snapshot/restore workflow, troubleshooting common issues, and CI/CD integration. Use when initializing dependency management for a new R project, adding or updating packages, restoring an environment on a new machine, troubleshooting restore failures, or integrating renv with CI/CD pipelines.

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

Instrument applications with OpenTelemetry for distributed tracing, including auto and manual instrumentation, context propagation, sampling strategies, and integration with Jaeger or Tempo. Use when debugging latency issues in distributed systems, understanding request flow across microservices, correlating traces with logs and metrics for root cause analysis, measuring end-to-end latency, or migrating from legacy tracing systems to OpenTelemetry.

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

Investigate root causes and manage CAPAs (Corrective and Preventive Actions) for compliance deviations. Covers investigation method selection (5-Why, fishbone, fault tree), structured root cause analysis, corrective vs preventive action design, effectiveness verification, and trend analysis. Use when an audit finding requires a CAPA, when a deviation or incident occurs in a validated system, when a regulatory observation needs a formal response, when a data integrity anomaly requires investigation, or when recurring issues suggest a systemic root cause.

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

Design sustainable on-call rotations with balanced schedules, clear escalation policies, fatigue management, and handoff procedures. Minimize burnout while maintaining incident response coverage. Use when setting up on-call for the first time, scaling a team from 2-3 to 5+ engineers, addressing on-call burnout or alert fatigue, improving incident response times, or after a post-mortem identifies handoff issues.

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

Implement AI-powered anomaly detection for operational metrics using time series analysis (Isolation Forest, Prophet, LSTM), alert correlation, and root cause analysis. Reduce alert fatigue by intelligently identifying true anomalies in system metrics, logs, and traces. Use when operations teams are overwhelmed by alert volume, when detecting complex multi-metric anomalies beyond static thresholds, when seasonal patterns make thresholds ineffective, or when needing to predict issues proactively before they impact users.

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

Remove dead code, unused imports, fix lint warnings, and normalize formatting across a codebase without changing business logic or architecture. Use when lint warnings have piled up during rapid development, unused imports and variables clutter files, dead code paths were never removed, formatting is inconsistent, or static analysis tools report fixable hygiene issues.

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

Conduct temperament-based health assessment from Hildegard von Bingen's Causae et Curae. Evaluates the four temperaments (sanguine, choleric, melancholic, phlegmatic), elemental correspondences (air, fire, earth, water), and provides dietary and lifestyle recommendations for rebalancing. Use when understanding constitutional type in Hildegardian terms, experiencing imbalance (fatigue, digestive issues, mental fog) needing holistic guidance, seeking dietary recommendations by temperament, or researching medieval humoral medicine.

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

Audit project dependencies for version staleness, security vulnerabilities, and compatibility issues. Covers lock file analysis, upgrade path planning, and breaking change assessment. Use before a release to ensure dependencies are current and secure, during periodic maintenance reviews, after receiving a security advisory, when upgrading to a new language version, before submitting to CRAN or npm, or when inheriting a project to assess its dependency health.

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

Report where a session missed moo's standard — the agent asks only while stating intent and shape, then works on its own — as issues a builder can act on. Pass a session id to report on a past session instead of this one.

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

Alternate /pr-review and /pr-address on a PR until the PR is truly mergeable — no new review findings, zero unresolved inline threads, zero unaddressed top-level reviews or issue comments, all CI checks green, and two consecutive quiet polls after CI settles. Use when the user wants a PR polished to merge-ready without setting a fixed number of rounds.

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

Review a PR for correctness, security, code quality, and testing issues. TRIGGER when user asks to review a PR, check PR quality, or give feedback on a PR.

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

Issue Greek invoices through AADE's timologio, get the MARK, keep one JSON per invoice, push it into the ERP (SAP Business One today; other adapters welcome) and email the PDF. Trigger on: τιμολόγιο, τιμολόγησε, έκδοση τιμολογίου, invoice, myDATA, timologio, MARK, ΤΠΥ, πελάτης ΑΦΜ, προεπισκόπηση τιμολογίου.

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

Use when adding telemetry, composing an observability surface, reviewing alerts, shipping a production feature, or diagnosing a production issue. Not for live failures, profiling, or launch runbooks.

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

Use when asked to create or update a PR, revise its description, or link issue references to its body. Not for multi-PR stacks: use gate-and-merge. Not for releases: use git-workflow-and-versioning.

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

Use when the user wants one-time repository setup for tracker, triage labels, and domain conventions. Not for ongoing triage, issue creation, or multi-repo setup.

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

Use when a redacted, trimmed agent transcript must be appended to a GitHub PR or issue body, with human approval and preview. Not for automated or model-initiated insertion.

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

Use when the user explicitly asks to choose which issues or pull requests to close interactively. Don't use for closing items without per-item selection and explicit approval.

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

Use when the user asks "where to help", "contribution opportunities", or "find a good first issue". Returns data-backed first steps. Not for PR review queues: use gh-review-requests.

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

Use when a trusted bug or performance report needs reproduction and fix. Not for untrusted reports or scope beyond the named feature.

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

Audit one bounded Proto UI collaboration-governance slice and route policy-determined drift toward reversible correction. Use across Issues, pull requests, Discussions, labels, milestones, Project, rules, permissions, or Actions. This evidence leaf is read-only; authorized corrections continue in their registered leaves.

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

Measure the active Agent model with pinned offline ModelTrace sampling and return an unsigned closed-set attribution record. Use before Agent-originated commits, Issue/PR creation or material updates, comments, reviews, and current collaboration writes in either execution mode. Do not treat a fingerprint, declared model label, or record reference as authenticated identity, permission, independent review, or acceptance.

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

Apply one exact-target Proto UI collaboration update through the ordinary governed primitive or an explicitly current-user connected-operation path for archive/ref recovery, Issue reopening/linking, additive carrier publication and service control. Do not manufacture review dispositions, merge, close, release or change privileged settings.

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