「issue」の検索結果

Review source files changed during a phase for bugs, security issues, and code quality problems

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

Autonomous audit-to-fix pipeline — find issues, classify, fix, test, commit

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

Write minimal, reliable bug reproducers (repros) for any project. Use when: (1) a bug report or issue needs a test that reliably demonstrates the failure, (2) converting a described failure scenario into runnable code, (3) minimizing an existing complex test to its essential trigger conditions. Covers the full repro workflow: failure characterization, scope selection, writing the repro, verifying it fails for the right reason, and minimizing to the smallest possible trigger.

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

Comprehensive guide for writing Apache Cassandra in-JVM distributed tests (dtests). Use when creating tests that simulate multi-node Cassandra clusters within a single JVM for faster integration testing. Covers cluster creation (single-node, multi-node, multi-datacenter), configuration (all cassandra.yaml parameters, features, network topology), instance lifecycle (startup/shutdown/restart), query execution, message filtering for failure scenarios, running code on instances, ClusterUtils utilities, and debugging classloader-related issues (serialization failures, same-class-different-classloader problems).

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

Refresh Claude Ads platform, API, policy, regulation, benchmark, issue, pull-request, fork, and repository evidence. Use for ads research refresh, expired refresh_due dates, stale API or platform claims, reverify-or-demote decisions, release-current claim validation, ecosystem review, current platform changes, or updating paid-media knowledge.

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

Deeper risk assessment for a single feature or product area when the launch review found something that needs more than a line item. Structured analysis: what could go wrong, how likely, how bad, what mitigates it. Use when user says "deep dive on this risk", "risk assessment for [feature]", "what could go wrong with", or when launch-review flags a novel issue.

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

Draft a brief section in house style, consistent with the case theory — every fact cited, every case checked, every argument tied to the theory. Use when the user says "draft the [section]", "write the statement of facts", "argument section on [issue]", or needs a first draft of a brief section.

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

Full launch review against your framework and risk calibration. Use when the user says "review this launch", "legal review for [feature]", "can we ship this", "what are the legal issues with [product]", or references a launch tracker ticket or PRD that needs a category-by-category review memo.

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

Grade an IRAC essay for structure, issue-spotting, rule accuracy, analysis depth, and organization. Does NOT rewrite the essay or show a model answer; tracks patterns across sessions. Use when the user says "grade my IRAC", "check my essay", or "I wrote this, give me feedback".

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

Structured intake — practice-area templates, cross-area issue spotting, conflict flags, and triage classification. Produces a formatted case summary the student analyzes and the professor reviews. Does NOT decide case acceptance. Use when starting a new client intake, running an intake interview, or writing up a new client's situation.

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

Analyze past exams from the same professor to surface patterns — subject weighting, recurring issue-spot traps, favored hypo types, policy-vs-doctrine mix — and forecast likely emphases for the upcoming exam. Use when the user says "what's on the exam", "analyze past exams", "predict the exam", or shares past exams.

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

Ask questions against an open investigation log — what witnesses said, where accounts conflict, what gaps exist, what the strongest evidence is on each issue. Use when the attorney needs to query the investigation record without re-reading every entry.

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

Detects when Luminance, Kira, or a similar bulk-review tool is in use, hands off the high-volume clause extraction to it, and QAs its output per the trust level in `~/.claude/plugins/config/claude-for-legal/corporate-legal/CLAUDE.md`. Use when user says "send to Luminance", "bulk review", "AI extraction", or when diligence-issue-extraction hits a high-volume category.

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

Use when reviewing, triaging, validating, or discussing ClawHub GitHub issues or pull requests, including author context, CI, UI proof, evidence, labels, close decisions, and maintainer handoff.

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

Audit a datafusion-spark function implementation for correctness against Apache Spark 4.2.0. Studies the Spark source across versions, reviews the Rust implementation and its signature, verifies expected values against a real PySpark, fixes divergences, and captures the rest as issues and disabled tests.

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

Guides the contribution workflow for Apache Beam, including creating PRs, issue management, code review process, release cycles, and rigorous evaluation rules for high-risk core component changes. Use when contributing code, creating PRs, or modifying core Beam components.

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

Guides understanding and working with Apache Beam runners (Direct, Dataflow, Flink, Spark, etc.). Use when configuring pipelines for different execution environments or debugging runner-specific issues.

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

Guides development and usage of I/O connectors in Apache Beam. Use when working with I/O connectors, creating new connectors, or debugging data source/sink issues.

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

Guides understanding and using the Gradle build system in Apache Beam. Use when building projects, understanding dependencies, or troubleshooting build issues.

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

Create Gentle AI pull requests with issue-first checks. Trigger: creating, opening, or preparing PRs for review.

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

Write warm, direct collaboration comments. Trigger: PR feedback, issue replies, reviews, Slack messages, or GitHub comments.

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

Create Gentle AI pull requests with issue-first checks. Trigger: creating, opening, or preparing PRs for review.

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

Reliably run TypeScript type-checking (npx tsc --noEmit) by using shell_agent as a fallback when run_shell fails due to environment or timeout issues.

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

Diagnose and resolve file access issues by first verifying the directory structure.

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