「artifact」の検索結果

Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.

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

Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.

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

Execute the implementation planning workflow using the plan template to generate design artifacts.

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

시각 + 브랜드 일관성 리뷰. HTML/MD/JSX artifact를 받아 brand DESIGN.md 대비 typo hierarchy, 색 budget, radius scale, 컴포넌트 state, 모바일 반응형 검수. severity BLOCK/WARN/FYI + line ref 출력. 'UI 리뷰', '디자인 검토', 'DESIGN.md 대비 검수' 류 트리거.

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

Phase transition validation with artifact checklists, PASS/FAIL/CONDITIONAL gates for workflows

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

GitHub Actions workflow patterns, matrix builds, caching strategies, deployment pipelines, artifact management, and rollback procedures.

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

Scan code changes for security vulnerabilities using Bug Hunter-native artifacts and STRIDE context. Use whenever the user asks for PR security review, commit-diff scanning, staged-change security checks, branch-comparison security review, or pre-merge security analysis of changed code.

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

Run a focused STRIDE-based security review using Bug Hunter-native artifacts. Use whenever the user asks for a full security audit, repository security review, weekly security scan, PR security review with deeper validation, or wants dependency CVEs and threat-model context combined into one workflow.

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

Generate or refresh a STRIDE-based threat model for the current repository using Bug Hunter-native artifacts. Use whenever the repository has no threat model yet, the architecture changed materially, a security review needs fresh trust-boundary context, or the user explicitly asks for a threat model.

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

Validate security findings for exploitability, reachability, and real-world impact using Bug Hunter-native findings artifacts. Use after security scans, before patch generation, or whenever the user wants confirmation that a suspected vulnerability is actually exploitable.

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

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.

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

Initialize a missing research Workspace from the repository template without overwriting existing Run state; use before Pipeline binding when the target under `workspaces/` has no valid core artifacts.

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

Execute exactly one eligible Unit in an existing research Workspace; use for stepwise or manual semantic execution when status, Attempt, Artifact, Manifest, checkpoint, and acceptance evidence must remain synchronized.

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

Draft non-prose visuals artifacts (timeline, figure specs) for a survey, grounded in evidence and using citation keys from `citations/ref.bib`.

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

Post-merge paper-voice gate: inspect the reader-facing draft for planner-talk and axis-label artifacts, then route fixes to the actual source.

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

Fetch and normalize supported source-tutorial inputs into local, traceable text artifacts.

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

Review and record one pending human checkpoint in a research Workspace; use when a HUMAN Unit is blocked on an `Approve C*` decision, and never treat silence or artifact existence as approval.

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

Project completed stage Artifacts into a concise human-review block in `DECISIONS.md`; use before a Workflow checkpoint, not for Workflow routing or approval.

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

Use when `paper-review` needs a canonical manuscript text artifact before claim extraction.

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

Automatically fix broken OpenCLI adapters when commands fail. Load this skill when an opencli command fails — it guides you through collecting a trace artifact, patching the adapter, retrying, and filing an upstream GitHub issue after a verified fix. Works with any AI agent.

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

Guide developers through capturing diagnostic artifacts to diagnose production .NET performance issues. Use when the user needs help choosing diagnostic tools, collecting performance data, or understanding tool trade-offs across different environments (Windows/Linux, .NET Framework/modern .NET, container/non-container).

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

Establish MSBuild/.NET build performance baselines before optimizing. USE FOR: a .NET build or solution that is slow or has build-performance concerns; cold, warm, incremental, or no-op measurements; before/after comparisons; CI build output caching; static graph build decisions; artifacts output; and dependency graph trimming. Start here before build-perf-diagnostics, incremental-build, or build-parallelism. DO NOT USE for webpack, npm, JavaScript bundlers, or other non-MSBuild build systems. For detailed target/task/analyzer bottleneck analysis after baselining, use build-perf-diagnostics.

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

Own concrete MSBuild ItemGroup and item-expression questions. USE FOR: Include, Remove, Update, item identity and metadata, transforms, filtering, batching, duplicate or overlapping items, and reviews that verify whether those operations are correct. Generated items stay in scope when the central defect is item identity, metadata, batching, duplicate declarations, or glob/Remove/Update semantics. For a generated artifact missing from compilation or output, wrong target timing/path, or FileWrites clean tracking without a broader item-semantics defect, use including-generated-files. The item operation may be broken, suspected, or already correct. Exclude property-only issues, general incrementality with no item question, broad reviews with no concrete item concern, and non-MSBuild systems.

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

Use the open-source free `Asynkron.Profiler` dotnet tool for CLI-first CPU, allocation, exception, contention, and heap profiling of .NET commands or existing trace artifacts. USE FOR: Asynkron.Profiler setup; automation-friendly profiling output; CPU, allocation, exception, contention, and heap investigation. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.

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