What is doc-from-jira?

A command that turns a Jira ticket into a structured documentation file. Jira is a tool for tracking work; this command reads tickets in the DOCS project and uses their requirements to prepare the document.

Use it when starting documentation from a DOCS Jira ticket, especially when the ticket includes acceptance criteria, specifications, or engineering links.

It removes the blank-page problem and keeps the document tied to the ticket’s requirements. It can also add the document to navigation and update the ticket’s status with approval.

How SumoLogic/sumologic-documentation configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to SumoLogic/sumologic-documentation. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/SumoLogic/sumologic-documentation/main/.claude/commands/doc-from-jira.md

Clone the repo

git clone --depth 1 https://github.com/SumoLogic/sumologic-documentation

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/sumologic/sumologic-documentation/doc-from-jira/github.svg)](https://agentmods.dev/commands/sumologic/sumologic-documentation/doc-from-jira)

Your own site

<a href="https://agentmods.dev/commands/sumologic/sumologic-documentation/doc-from-jira"><img src="https://agentmods.dev/badge/commands/sumologic/sumologic-documentation/doc-from-jira/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/sumologic/sumologic-documentation/doc-from-jira"><img src="https://agentmods.dev/badge/commands/sumologic/sumologic-documentation/doc-from-jira.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 2,697 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.02697
Opus 5.5	$0.00000	$0.01079
Sonnet 5.5	$0.00000	$0.00539
Haiku 4.5	$0.00000	$0.00270

Measured 16d ago against content hash 2bb05b4da42c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

doc-from-jira scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 16d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/commands/doc-from-jira.md · 360 lines

How it starts

The opening of the file, as written. The whole thing — 360 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Doc from Jira — Scaffold a Doc from a Jira Ticket

Pulls a Jira ticket from the DOCS project, extracts the content requirements, and scaffolds a fully structured documentation file ready for writing. Eliminates the blank-page problem and keeps the doc aligned with the ticket spec from the start.

What this command does

When you invoke /doc-from-jira, Claude will:

Fetch the Jira ticket. Pull title, description, acceptance criteria, and linked resources
Determine doc type. Feature, how-to, concept, reference, or troubleshooting
Infer the file path. Based on the technical area and content type
Scaffold the doc. Generate a file with correct frontmatter, structure, and placeholder sections pre-populated from the ticket
Update sidebars.ts. Add the new doc to navigation (with user approval)
Link back to Jira. Set the Jira ticket to In Progress if not already

When to use this command

Starting a new doc for a DOCS ticket
When a ticket has a detailed description or acceptance criteria worth preserving
For tickets with linked specs, PRDs, or engineering docs to pull context from
When you want to ensure the doc structure is aligned with what was requested

When NOT to use this command

App integrations — use /app-doc instead
Cloud-to-Cloud sources — use /c2c-source-doc instead
Release notes — use the appropriate /release-note-* command instead
Tickets that do not require a net-new doc (pure updates, typo fixes)

Workflow

Step 1: Get the ticket number

If the user provides a ticket number (e.g., DOCS-1234), use it directly.

If the user says "use my current ticket" or "use the branch ticket", extract the ticket number from the current git branch name (pattern: DOCS-\d+).

If no ticket is found, ask the user for the ticket number.

Step 2: Fetch the ticket

Use the Jira MCP tool to fetch the ticket:

Cloud ID: 247075db-3b0b-4f1b-92cb-51683ab743a6
Issue key: the provided DOCS-XXXX number

Read the full file on GitHub · 360 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

16d ago Changed 2bb05b4da42c
2mo ago First seen · 360 lines · 0 tokens per session scan A 996568f4de3a

Subscribe to this mod's changes

doc-from-jira is a command published in the GitHub repository SumoLogic/sumologic-documentation (42 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,697 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Planning Productivity React Writing and docs documentation open-source

doc-from-jira next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
doc-from-jiraSumoLogic/sumologic-documentation	Command	42	yesterday	MIT	A	0	Claude Code
resume-cover-letterjezweb/claude-skills	Command	1.1k	28d ago	MIT	A	12	Claude Code
quotetdimino/claude-code-minoan	Command	41	yesterday	MIT	A	0	Claude Code
cliJNTMTMTM/eIsland	Command	335	yesterday	GPL-3.0	A	0	Claude Code
canvasAgriciDaniel/claude-canvas	Command	303	7mo ago	MIT	A	25	Claude Code
gpd:settingspsi-oss/get-physics-done	Command	973	3mo ago	none	A	36	Claude Code
gpd:updatepsi-oss/get-physics-done	Command	973	3mo ago	none	A	14	Claude Code

sumologic-documentation: Command for Claude Code