pre-done

Validate ticket and PR readiness with branch, review, test, QA, and Jira gates.

Updated Aug 23, 2026

Search Tags:#automation #workflow #jira #ci-cd #gate #pre-done

Ready to run

npx skills add https://github.com/Great-Gray-Group/devops-skills --skill pre-done

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pre-done
Source: https://github.com/Great-Gray-Group/devops-skills/tree/main/pre-done
Command: npx skills add https://github.com/Great-Gray-Group/devops-skills --skill pre-done

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates that all required gates pass before a ticket or PR is marked Done, ensuring quality and preventing premature closures in software delivery.

Core Features & Use Cases

Gate-driven checks across Jira tickets and GitHub PRs to enforce Done criteria.
Integrates with Git, Jira, and PR workflows to automatically verify branch state, tests, browser QA, and ticket status.
Use Case: Before merging a PR or transitioning a Jira issue, run /pre-done to guarantee all gates pass and generate a transparent right-to-know report.

Quick Start

Invoke /pre-done with a Jira key and optional service name to execute all gates before closing the ticket or merging the PR.

Frequently Asked Questions about pre-done

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I enforce completion gates before a Jira ticket is transitioned to Done?▼

To enforce completion gates before transitioning to Done, run a validation sequence that checks branch state, PR reviews, tests, browser QA, and Jira status. This prevents premature closures by ensuring all release readiness criteria pass.

How do I prevent premature PR merges in a CI-CD workflow?▼

To prevent premature PR merges in a CI-CD workflow, validate ticket and PR readiness by running sequential gates for branch state, tests, browser QA, and Jira status. This generates a structured report verifying all conditions pass before closure.

What is a gate-driven check for software delivery release readiness?▼

A gate-driven check for release readiness is a validation sequence that verifies branch state, PR reviews, tests, browser QA, Jira status, and work tree cleanliness before transitioning a ticket to Done. It coordinates GitHub and Jira to prevent premature closures.

Can I automatically verify Jira state and GitHub PR status at the same time before release?▼

Yes, you can automatically verify Jira state and GitHub PR status together before release by running a coordinated gate sequence. It checks both platforms alongside local tests and branch conditions to produce a structured gate report for downstream actions.

How do I run pre-done validation checks with a Jira key?▼

To run pre-done validation checks, invoke the command with a Jira key and an optional service name. This executes the full sequence of gates across Git, Jira, and PR workflows to guarantee all readiness criteria pass before merging or closing.

Does the gate validation process require a clean work tree to pass?▼

Yes, the gate validation process requires a clean work tree to pass. It runs a sequence of checks including branch state, PR reviews, tests, browser QA, Jira state, and work tree cleanliness to ensure complete release readiness before transitioning to Done.