Stats
Actions
Tags
From jira
Validates Jira ticket acceptance criteria via user prompts and transitions to Done if all complete. Invoke with /complete PROJ-123 during ticket closure.
How this skill is triggered — by the user, by Claude, or both
Slash command
/jira:completeThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
jira:complete - Mark a Jira ticket as complete after validating acceptance criteria
jira:complete - Mark a Jira ticket as complete after validating acceptance criteria
/complete [arguments]
Mark a Jira ticket as complete after validating acceptance criteria
Complete a Jira ticket by validating acceptance criteria and transitioning to Done.
Usage: /complete PROJ-123
Steps:
atlassian_get_issue to fetch ticket details including description and commentsatlassian_add_comment to add completion summaryatlassian_transition_issue to transition to "Done"Display Format:
✅ Completing PROJ-123: {summary}
📋 Acceptance Criteria Validation:
1. ✓ {criterion 1} - COMPLETE
2. ✓ {criterion 2} - COMPLETE
3. ✗ {criterion 3} - INCOMPLETE
4. ✓ {criterion 4} - COMPLETE
❌ Cannot complete: 1 criterion not met
- {criterion 3}
Suggestion: Complete remaining criteria before marking as Done.
Only transition to Done if ALL criteria are validated.
npx claudepluginhub thebushidocollective/han --plugin jiraValidates Jira ticket acceptance criteria without status changes. Checks progress via comments/code evidence, summarizes completion, and suggests remaining work. Use /validate TICKET-ID.
Validates Linear issue acceptance criteria via user prompts and marks complete with comment if all met; lists incompletes otherwise. Invoke via /complete ISSUE-ID.
Retrieves, analyzes, and updates Jira tickets via MCP or direct REST API. Useful for fetching requirements, transitioning status, adding comments, and linking work items.