You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Do NOT use old slash-command syntax (e.g., `/jira-reader --issue PROJ-123`).
36
52
53
+
### When to use each approach
54
+
55
+
| Approach | When to use | Examples |
56
+
|---|---|---|
57
+
|`python3 ${CLAUDE_PLUGIN_ROOT}/...`| Running a script to fetch data, post comments, detect state |`git_pr_reader.py info`, `jira_reader.py`, `callouts.rb`|
58
+
|`Skill: plugin:skill`| Loading full skill knowledge — rules, checklists, domain expertise the LLM applies |`rh-ssg-formatting`, `ibm-sg-punctuation`, review skills |
@@ -622,18 +622,18 @@ Requires tokens in `~/.env`:
622
622
623
623
### Reading Red Hat documentation with redhat-docs-toc
624
624
625
-
Research existing Red Hat documentation to understand patterns and gaps. Use the `docs-tools:redhat-docs-toc` skill to extract article URLs from documentation TOC pages:
625
+
Research existing Red Hat documentation to understand patterns and gaps. Extract article URLs from documentation TOC pages:
After fetching the primary ticket with jira-reader, run the ticket graph traversal to gather bounded context (1 level deep) from the ticket's relationships:
The `--graph` flag discovers custom field IDs, fetches the parent, children, siblings, issue links, and web/remote links, then classifies URLs by type. It uses `JIRA_AUTH_TOKEN` and `JIRA_EMAIL` from the environment (with `~/.env` fallback) and `JIRA_URL` (default: `https://redhat.atlassian.net`).
@@ -424,46 +424,46 @@ If a traversal step failed due to a permission error (e.g., 403 on parent), note
424
424
425
425
### Querying JIRA with jira-reader
426
426
427
-
Use the Skill tool to invoke the `docs-tools:jira-reader` skill. Do not call `jira_reader.py`directly.
0 commit comments