ninja-agents

Add missing Activity Type field to completed Jira tickets. Fetches tickets matching a configured JQL filter, classifies each ticket's Activity Type based on issue type, labels, and summary keywords, previews proposed changes, and applies them after user approval. Trigger phrases: "add missing activity type", "fill activity type", "set activity type", "classify activity type", "activity type updater". <example> user: "/jira-add-missing-activity-type" assistant: "I'll fetch Done tickets missing Activity Type, classify them, and preview the proposed assignments." </example> <example> user: "/jira-add-missing-activity-type" assistant: "Reading config... Found 23 tickets missing Activity Type. Classifying based on rules..." </example>

Find resolved bugs missing a QA Contact and identify the verifier from comments and status transitions. Previews proposed assignments and applies them after user approval. Trigger phrases: "bugs missing QE", "missing QA contact", "find QE for bugs", "set QA contact", "bugs without QE". <example> user: "/jira-bugs-missing-qe" assistant: "I'll fetch resolved bugs missing QA Contact, analyze comments and changelogs to identify verifiers, and preview proposed assignments." </example> <example> user: "/jira-bugs-missing-qe" assistant: "Reading config... Found 14 bugs missing QA Contact. Analyzing comments and transitions..." </example>

Generate a QE (Quality Engineering) story from a dev Jira story. Reads the dev story, optionally reads repo context for richer acceptance criteria, generates QE description with test scenarios, previews for approval, then creates the story in Jira and links it. Trigger phrases: "qe story", "create qe story", "generate qe story", "qe acceptance criteria", "quality story from dev story". <example> user: "/jira-qe-story CNV-12345" assistant: "I'll read the dev story CNV-12345 and generate a QE story for it." </example> <example> user: "/jira-qe-story MTV-5678 --repo kubev2v/forklift-console-plugin" assistant: "I'll read MTV-5678 and use the forklift-console-plugin repo for context." </example>

Transition Jira sprint tickets based on linked GitHub PR/issue status. Fetches all tickets in a sprint, checks their linked GitHub PRs and issues, previews proposed status transitions, and applies them after user confirmation. Trigger phrases: "update sprint tickets", "transition tickets", "sync ticket status", "update jira from PRs", "sprint ticket updater". <example> user: "/jira-sprint-tickets-updater" assistant: "I'll fetch the active sprint tickets, check linked PRs/issues, and propose status transitions." </example> <example> user: "/jira-sprint-tickets-updater" assistant: "Reading config... Found 32 tickets in Sprint 5. Checking linked PRs and issues..." </example>

Estimate story points for unpointed Jira tickets by comparing against historical team data. Fetches Done tickets with SP from Jira, caches them locally, then uses Claude's reasoning to suggest SP values for new tickets. Adds a Jira comment with justification and sets the SP field. Trigger phrases: "estimate story points", "story point estimation", "SP estimation", "estimate SP", "point tickets", "size tickets". <example> user: "/jira-story-points CNV-12345" assistant: "I'll estimate story points for CNV-12345 by comparing it against historical team data." </example> <example> user: "/jira-story-points" assistant: "I'll find unpointed tickets in the backlog and estimate story points for each." </example>

Audit a repository for foundational docs (README, CONTRIBUTING, AGENTS, ARCHITECTURE) and AI tooling config, then scaffold missing files in one pass

1 hook across 1 event