Anchor Repro
lynxlangya/techne
Reproduce a behavioral bug before fixing it, record the failing probe, and verify the fix with the same probe.
Create structured Jira tickets for Dynamo from bug reports, failing tests, or feature requests.
Install Dynamo Jira Ticket
$ npx skills add DynamoDS/Dynamo --skill dynamo-jira-ticket -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install DynamoDS/Dynamo dynamo-jira-ticket --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/DynamoDS/Dynamo.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/dynamo-jira-ticket .claude/skills/dynamo-jira-ticket && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "dynamo-jira-ticket" agent skill from https://github.com/DynamoDS/Dynamo/tree/master/.claude/skills/dynamo-jira-ticket into .claude/skills/dynamo-jira-ticket/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dynamo-jira-ticket", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/DynamoDS/Dynamo/tree/master/.claude/skills/dynamo-jira-ticketType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add DynamoDS/Dynamo --skill dynamo-jira-ticket -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install DynamoDS/Dynamo dynamo-jira-ticket --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/DynamoDS/Dynamo.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/dynamo-jira-ticket .agents/skills/dynamo-jira-ticket && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "dynamo-jira-ticket" agent skill from https://github.com/DynamoDS/Dynamo/tree/master/.claude/skills/dynamo-jira-ticket into .agents/skills/dynamo-jira-ticket/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dynamo-jira-ticket", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add DynamoDS/Dynamo --skill dynamo-jira-ticket -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install DynamoDS/Dynamo dynamo-jira-ticket --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/DynamoDS/Dynamo.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/dynamo-jira-ticket .cursor/skills/dynamo-jira-ticket && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "dynamo-jira-ticket" agent skill from https://github.com/DynamoDS/Dynamo/tree/master/.claude/skills/dynamo-jira-ticket into .cursor/skills/dynamo-jira-ticket/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dynamo-jira-ticket", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/DynamoDS/Dynamo.git --path .claude/skills/dynamo-jira-ticket--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add DynamoDS/Dynamo --skill dynamo-jira-ticket -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install DynamoDS/Dynamo dynamo-jira-ticket --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/DynamoDS/Dynamo.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/dynamo-jira-ticket .gemini/skills/dynamo-jira-ticket && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "dynamo-jira-ticket" agent skill from https://github.com/DynamoDS/Dynamo/tree/master/.claude/skills/dynamo-jira-ticket into .gemini/skills/dynamo-jira-ticket/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dynamo-jira-ticket", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install DynamoDS/Dynamo dynamo-jira-ticketInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add DynamoDS/Dynamo --skill dynamo-jira-ticket -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/DynamoDS/Dynamo.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/dynamo-jira-ticket .github/skills/dynamo-jira-ticket && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "dynamo-jira-ticket" agent skill from https://github.com/DynamoDS/Dynamo/tree/master/.claude/skills/dynamo-jira-ticket into .github/skills/dynamo-jira-ticket/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dynamo-jira-ticket", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add DynamoDS/Dynamo --skill dynamo-jira-ticket -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install DynamoDS/Dynamo dynamo-jira-ticket --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/DynamoDS/Dynamo.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/dynamo-jira-ticket .opencode/skills/dynamo-jira-ticket && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "dynamo-jira-ticket" agent skill from https://github.com/DynamoDS/Dynamo/tree/master/.claude/skills/dynamo-jira-ticket into .opencode/skills/dynamo-jira-ticket/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dynamo-jira-ticket", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
dynamo-jira-ticket- GitHub stars
- 2k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 279 words
- Files
- 2 (incl. assets)
- Skills in repo
- 13
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Create structured Jira tickets for Dynamo from bug reports, failing tests, or feature requests.
- Works in 3 steps: Gather evidence first. Before writing,… → Write the ticket using… → Review -- ensure every section has…
- Writing a Jira ticket
- SKILL.md covers When to use, When not to use, Inputs expected and Output format, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Dynamo Jira Ticket is an agent skill from DynamoDS/Dynamo. Create structured Jira tickets for Dynamo from bug reports, failing tests, or feature requests. Use this skill whenever writing a Jira ticket, triaging a bug, turning a vague issue into an actionable ticket, or writing acceptance criteria. Also use when the user mentions "file a ticket", "write a bug report", or "create a Jira issue" for Dynamo.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including assets (for example `assets/template.md`).
It sits in Testing & QA, covering QA and bug reports, Failing and flaky tests and User stories. It works with Jira. The repository describes itself as: Open Source Graphical Programming for Computational Design and Automation. The licence is Apache-2.0.
When your agent uses it
- Writing a Jira ticket
- Turning a vague issue into an actionable ticket
- Writing acceptance criteria
- The user mentions file a ticket
Example prompts
- “file a ticket”
- “write a bug report”
- “create a Jira issue”
- “/dynamo-jira-ticket”
Requirements
- Python 3
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Gather evidence first. Before writing, check the codebase for supporting details
- Write the ticket using ./assets/template.md in this folder.
- Review -- ensure every section has concrete, verifiable content. No vague language.
What it can do on your machine
Read from SKILL.md and the folder at commit 72b753c. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Dynamo Jira Ticket loads about 1.1k tokens when it runs. Until then it costs about 92 tokens; SKILL.md has 279 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from DynamoDS/Dynamo at commit 72b753c, republished under its Apache-2.0 licence (© DynamoDS). 279 words, ~1,059 tokens.
Download SKILL.mdSave it as
.claude/skills/dynamo-jira-ticket/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- dynamo-jira-ticket
- description
- Create structured Jira tickets for Dynamo from bug reports, failing tests, or feature requests. Use this skill whenever writing a Jira ticket, triaging a bug, turning a vague issue into an actionable ticket, or writing acceptance criteria. Also use when the user mentions "file a ticket", "write a bug report", or "create a Jira issue" for Dynamo.
Dynamo Jira Ticket
When to use
- Creating a new Jira ticket from a bug report, failing test, or code investigation.
- Refining a vague issue description into a structured, actionable ticket.
- Writing acceptance criteria from a feature request or design discussion.
When not to use
- PR descriptions -- use dynamo-pr-description instead.
- Architecture questions -- use dynamo-onboarding instead.
Inputs expected
A bug description, error log, failing test output, feature request, or code investigation findings.
Output format
A complete Jira ticket body ready to paste, following the canonical template in template.
Workflow
- Gather evidence first. Before writing, check the codebase for supporting details:
- For node issues: check the node implementation in
src/Libraries/orsrc/DynamoCore/. - For engine issues: check
src/Engine/ProtoCore/andsrc/Engine/ProtoScript/. - For UI issues: check
src/DynamoCoreWpf/and the relevant view extension. - For PublicAPI errors: check
PublicAPI.Unshipped.txt/PublicAPI.Shipped.txtin the affected project. - For test failures: read the NUnit test output and the relevant test file.
- For node issues: check the node implementation in
- Write the ticket using
./assets/template.mdin this folder. - Review -- ensure every section has concrete, verifiable content. No vague language.
Writing Rules
- Title: short, concrete, behavior-focused. Bad: "Dynamo crash". Good: "DynamoSandbox crashes on startup when global.json specifies missing SDK version".
- Prefer behavior over implementation: describe what the user sees, not internal class names.
- Include evidence: paste error messages, stack traces, screenshots. Trim to relevant lines.
- Separate facts from assumptions: if you're guessing at root cause, say so explicitly.
- Acceptance criteria must be testable: each criterion should be verifiable by running a test or checking a specific behavior.
Ticket Template
Use the canonical template at ./assets/template.md in this folder.
Required sections in each generated ticket:
- Title
- Problem
- Expected Behavior
- Repro Steps
- Impact
- Acceptance Criteria
- Investigation Notes
Example: Good ticket
# [DYN-5678] String.FromObject node returns null for custom Python class instances
## Problem
When a Python Script node returns a custom class instance, passing it to `String.FromObject` produces `null` instead of calling `__str__` or `ToString()`. This breaks downstream string operations.
## Expected Behavior
`String.FromObject` should call the object's `ToString()` method (or Python `__str__`) and return the string representation, consistent with how it handles built-in types.
## Repro Steps
1. Open Dynamo Sandbox
2. Create a Python Script node with: `class Foo:\n def __str__(self): return "hello"\nOUT = Foo()`
3. Connect output to a `String.FromObject` node
4. Run the graph
5. Expected: `String.FromObject` outputs `"hello"`
6. Actual: `String.FromObject` outputs `null`
## Impact
- **Users affected**: Users with Python-heavy workflows using custom classes
- **Frequency**: Always (deterministic)
- **Severity**: Major (breaks string formatting workflows)
## Acceptance Criteria
- [ ] `String.FromObject` returns `__str__` result for Python objects with `__str__` defined
- [ ] `String.FromObject` returns `ToString()` result for .NET objects with custom `ToString()`
- [ ] NUnit test added in `test/Libraries/CoreNodesTests/StringTests.cs`
- [ ] No regression on built-in types (int, float, list, dict)
## Investigation Notes
- **Relevant files**: `src/Libraries/CoreNodes/String.cs`, `src/Engine/ProtoCore/`
- **Root cause hypothesis**: The engine may be wrapping the Python return value in a way that loses the original type's `ToString()` override© DynamoDS, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (assets) in .claude/skills/dynamo-jira-ticket of DynamoDS/Dynamo.
- SKILL.md
- assets/template.md
Open the folder on GitHubat commit 72b753c
Compare with similar skills
Dynamo Jira Ticket next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Dynamo Jira Ticket this skillDynamoDS/Dynamo | 2k | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Anchor Reprolynxlangya/techne | 105 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Build Scenario Teststamdogood/builder-essential-skills | 220 | — | ~1.7k | Automated safety check: Pass | MIT | |
| Test Case Managementpetrkindlmann/qa-skills | 168 | — | ~5k | Automated safety check: Pass | MIT | |
| Issue TracerZaxbyHub/opencode-swarm | 493 | — | ~383 | Automated safety check: Pass | MIT | |
| Issue TracerZaxbyHub/opencode-swarm | 493 | — | ~397 | Automated safety check: Pass | MIT |
Similar skills
Build Scenario Tests
tamdogood/builder-essential-skills
Inspect an unfamiliar repository, turn a focused Markdown behavior scenario into a deterministic test in the repository's native test stack, run it, and preserve traceability between intent and code.
Test Case Management
petrkindlmann/qa-skills
Author and maintain MANUAL and hybrid test cases and suites in TestRail, Xray (Jira), Zephyr Scale, and Qase.
Issue Tracer
ZaxbyHub/opencode-swarm
A skill your agent uses when asked to trace, investigate, root-cause, reproduce, plan, fix, resolve, close, or prepare a PR for an issue, bug report, defect, regression, failing test, or confusing…
Issue Tracer
ZaxbyHub/opencode-swarm
A skill your agent uses when asked to trace, investigate, root-cause, reproduce, plan, fix, resolve, close, or prepare a PR for an issue, bug report, defect, regression, failing test, or confusing…
Fix
avibebuilder/claude-prime
Fix bugs and broken behavior when there is enough evidence to act on a repair path.
More from DynamoDS/Dynamo
All 13 skills in this repoDynamo Dotnet Expert
DynamoDS/Dynamo
Write and review C/.NET code in Dynamo following Dynamo coding standards, modern C patterns, and repo conventions.
Dynamo PR Description
DynamoDS/Dynamo
Generate PR descriptions for Dynamo that align with the team template section names and order.
Dynamo Skill Writer
DynamoDS/Dynamo
Author and maintain Dynamo agent skills. An agent skill from DynamoDS/Dynamo.
Dynamo Unit Testing
DynamoDS/Dynamo
Write comprehensive NUnit tests for the Dynamo codebase following Dynamo testing patterns, conventions, and architectural constraints.
Dynamo UX Designer
DynamoDS/Dynamo
Plans UX flows, maps product needs to Weave Design System components, and generates structured Figma mockups using Autodesk Weave libraries.
Dynamo Webview Component Scaffold
DynamoDS/Dynamo
Scaffolds a new Dynamo package repo that hosts a view extension with a WebView2-embedded React frontend.
Related
Works with
Categories
Questions about Dynamo Jira Ticket
What does Dynamo Jira Ticket do?
Create structured Jira tickets for Dynamo from bug reports, failing tests, or feature requests. Dynamo Jira Ticket is an agent skill from DynamoDS/Dynamo. Create structured Jira tickets for Dynamo from bug reports, failing tests, or feature requests.
When should I use Dynamo Jira Ticket?
Dynamo Jira Ticket fits situations like: writing a Jira ticket; turning a vague issue into an actionable ticket; writing acceptance criteria; the user mentions file a ticket.
How do I install Dynamo Jira Ticket in Claude Code?
Run `npx skills add DynamoDS/Dynamo --skill dynamo-jira-ticket -a claude-code`. Or copy the skill folder (.claude/skills/dynamo-jira-ticket in DynamoDS/Dynamo) into .claude/skills/dynamo-jira-ticket in your project. Claude Code loads it when a task matches its description.
How do I install Dynamo Jira Ticket in Codex?
Run `npx skills add DynamoDS/Dynamo --skill dynamo-jira-ticket -a codex`. Or copy the skill folder (.claude/skills/dynamo-jira-ticket in DynamoDS/Dynamo) into .agents/skills/dynamo-jira-ticket in your project. Codex loads it when a task matches its description.
Can I use Dynamo Jira Ticket in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add DynamoDS/Dynamo --skill dynamo-jira-ticket -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/dynamo-jira-ticket, .gemini/skills/dynamo-jira-ticket, .github/skills/dynamo-jira-ticket and .opencode/skills/dynamo-jira-ticket in your project.
What does Dynamo Jira Ticket need to run?
SKILL.md names no scripts, command-line tools or credentials: Dynamo Jira Ticket is instructions for the agent only. Our summary lists: Python 3.
Does Dynamo Jira Ticket access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Dynamo Jira Ticket safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Dynamo Jira Ticket use?
Dynamo Jira Ticket is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Dynamo Jira Ticket use?
About 1.1k tokens (SKILL.md is roughly 4.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Dynamo Jira Ticket?
Skills that share tags, products or a category with Dynamo Jira Ticket: Anchor Repro (lynxlangya/techne, 105 stars), Build Scenario Tests (tamdogood/builder-essential-skills, 220 stars), Test Case Management (petrkindlmann/qa-skills, 168 stars) and Issue Tracer (ZaxbyHub/opencode-swarm, 493 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Dynamo Jira Ticket?
DynamoDS (a GitHub organization) maintains it in DynamoDS/Dynamo, which has 2,034 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on October 9, 2026.
Source: DynamoDS/Dynamo on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.