القائمة
File a GitHub bug issue against ai-dynamo/dynamo using context from the current conversation.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Start a debugging session with worklog file
Maintain Dynamo Fern docs site -- add, update, move, or remove pages. Use for any documentation changes.
Check CI status, analyze failures, and explain skips for a Dynamo PR
Generate optimized tool call parsers for dynamo from HuggingFace model chat templates. Use this when you need to add support for a new model's tool calling format. Takes a HuggingFace model name, analyzes its chat template, compares with existing parsers, and either maps to existing parser or generates new Rust code with tests for the dynamo tool_calling library.
| name | dynamo-bug |
| description | File a GitHub bug issue against ai-dynamo/dynamo using context from the current conversation. |
| user-invocable | true |
Use the current conversation context to file a well-structured bug report against ai-dynamo/dynamo via the gh CLI.
Gather context from the conversation. Review what the user has been working on, the problem encountered, error messages, logs, stack traces, and any reproduction steps already discussed. If critical details are missing, ask the user briefly — but prefer inferring from conversation context over asking.
Collect environment info. Determine whether the user is running in a Kubernetes or local development environment based on conversation context. Then gather the relevant environment details:
For Kubernetes environments:
For local development environments:
Use shell commands to auto-detect what you can (e.g., uname -m, python3 --version, nvidia-smi, kubectl version). Fill in what's available and mark unknowns as "N/A".
Draft the issue using this template and present it to the user for review before filing:
**Describe the Bug**
<clear, concise description>
**Steps to Reproduce**
1. ...
2. ...
<!-- Include relevant manifests or public container references if applicable -->
**Expected Behavior**
<what should have happened>
**Actual Behavior**
<what actually happened — include error messages, logs, or stack traces>
**Environment**
- **OS:** ...
- **Dynamo Runtime Version:** ...
- **CPU Architecture:** ...
- **CUDA Version:** ...
- **GPU Architecture:** ...
- **Python Version:** ...
<!-- Add K8s-specific fields if applicable -->
Show the draft to the user and ask for confirmation or edits before filing.
File the issue using:
gh issue create --repo ai-dynamo/dynamo --title "<title>" --body "<body>"
Return the issue URL to the user after creation.