[wallrj-cyberark]

Summary

twg jira workitem comment create can only add top-level comments. It has no option to reply inside an existing comment thread (#28). The skill does not say this, so agents look for a reply option and then post a top-level comment that has lost its link to the comment it answers.

This adds a short note to skills/twg-jira/references/workitems.md. It says that replies are not supported, and asks agents to start the new comment with a link to the comment they are answering and to mention its author.

Please remove this note when #28 is implemented. The skills here are synced from your internal source, so please also carry the change there, or the next sync will overwrite it.

Public Safety Checklist

• No tokens, credentials, cookies, auth files, or .env files.
• No private Jira, Confluence, Bitbucket, infrastructure, pipeline, or customer URLs.
• No customer data, proprietary content, or internal runbook detail.
• Generated docs/skills/plugins came from the release/public profile. (Hand-written change. See above.)
• Plugin or release metadata points to public TWG CLI docs and public CDN URLs.

Verification

• Checked twg jira workitem comment create --help: it has no parent or reply option. The request body it sends contains only body, properties and visibility.
• Ran the "Check for public-safety sensitive patterns" step from validate.yml locally. This change adds no matches. The step already fails on main because of two auth.conf references in skills/twg-bench-lite/scripts/benchmark-lite/runner.mjs.

[with Claude]

[atlassian-cla-bot]

Thank you for your submission! Like many open source projects, we ask that you sign our CLA (Contributor License Agreement) before we can accept your contribution.
If your email is listed below, please ensure that you sign the CLA with the same email address.

The following users still need to sign our CLA:
❌wallrj-cyberark

_{Already signed the CLA? To re-check, try refreshing the page.}