ワンクリックでManusで任意のスキルを実行

始める

tt-bug-report

スター330

フォーク50

更新日2026年3月31日 16:27

File a bug report with a reproducer against Tenstorrent repos (tt-lang, tt-metal, tt-xla)

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

tenstorrent

tenstorrent/tt-forge

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Task

File a bug report for a Tenstorrent issue. Gather context, minimize the reproducer, and create a GitHub issue in the right repo.

Where to File

Component	Repo
TT-Lang (DSL, compiler, kernels)	`tenstorrent/tt-lang`
TTNN (ops, tensor APIs, device)	`tenstorrent/tt-metal`
TT-Metal (low-level C++ kernels)	`tenstorrent/tt-metal`
TT-XLA (PyTorch/JAX frontend)	`tenstorrent/tt-xla`

If it's unclear which repo the bug belongs to, ask the user.

Input

$ARGUMENTS

Process

Step 1: Describe the Problem

Determine the type of issue and gather relevant info:

For crashes or incorrect results:

A reproducer script (even a non-minimal one is valuable)
Actual vs expected output

For compiler errors (tt-lang):

The full error message
Compiler flags used
MLIR before and after passes (/tmp/ttlang_initial.mlir, /tmp/ttlang_final.mlir)
Any other context that seems relevant

Step 2: Minimize the Reproducer

Ask the user if it's OK to upload the reproducer to the issue and spend some iterations trying to minimize it. If they agree, try to reduce it to the smallest script that still triggers the bug. Any reproducer is better than none -- if you can't minimize further, use what you have.

Step 3: File the Issue

Use gh to create an issue in the appropriate repo:

gh issue create --repo <owner/repo> \
  --title "[external bug report][from claude] <short title>" \
  --body "$(cat <<'EOF'
<body>
EOF
)"

The body should include:

Description of the problem
Reproducer (if available)
Error output / MLIR snippets (if applicable)
Environment context (simulator vs HW, etc.)

Output

Return the issue URL to the user.

このリポジトリの他の Skills

同じリポジトリ

tt-connect-remote-device

tenstorrent/tt-forge

Set up and verify remote connection to Tenstorrent hardware. Provides tools for running kernels, copying files, and reading logs on remote devices.

2026-03-31330

tt-enable-tracing

tenstorrent/tt-forge

TTNN trace capture and replay for eliminating dispatch overhead. Essential for real-time inference and multi-chip performance.

2026-03-31330

tt-lang-profile-optimize

tenstorrent/tt-forge

Profile and optimize TT-Lang kernels for performance. Covers auto-profiling, perf summary, signposts, and optimization workflow.

2026-03-31330

tt-lang

tenstorrent/tt-forge

Comprehensive TT-Lang DSL reference including programming model, APIs, hardware constraints, and guides for translating CUDA, Triton, PyTorch, or TTNN kernels

2026-03-31330

ttnn

tenstorrent/tt-forge

TTNN operations library reference for Tenstorrent hardware. Covers tensor APIs, ops catalog, model conversion from PyTorch, and memory/layout configuration.

2026-03-31330

name	tt-bug-report
description	File a bug report with a reproducer against Tenstorrent repos (tt-lang, tt-metal, tt-xla)
argument-hint	<description of the problem>

Task

File a bug report for a Tenstorrent issue. Gather context, minimize the reproducer, and create a GitHub issue in the right repo.

Where to File

Component	Repo
TT-Lang (DSL, compiler, kernels)	`tenstorrent/tt-lang`
TTNN (ops, tensor APIs, device)	`tenstorrent/tt-metal`
TT-Metal (low-level C++ kernels)	`tenstorrent/tt-metal`
TT-XLA (PyTorch/JAX frontend)	`tenstorrent/tt-xla`

If it's unclear which repo the bug belongs to, ask the user.

Input

$ARGUMENTS

Process

Step 1: Describe the Problem

Determine the type of issue and gather relevant info:

For crashes or incorrect results:

A reproducer script (even a non-minimal one is valuable)
Actual vs expected output

For compiler errors (tt-lang):

The full error message
Compiler flags used
MLIR before and after passes (/tmp/ttlang_initial.mlir, /tmp/ttlang_final.mlir)
Any other context that seems relevant

Step 2: Minimize the Reproducer

Step 3: File the Issue

Use gh to create an issue in the appropriate repo:

gh issue create --repo <owner/repo> \
  --title "[external bug report][from claude] <short title>" \
  --body "$(cat <<'EOF'
<body>
EOF
)"

The body should include:

Description of the problem
Reproducer (if available)
Error output / MLIR snippets (if applicable)
Environment context (simulator vs HW, etc.)

Output

Return the issue URL to the user.