Validate ticket and PR readiness with branch, review, test, QA, and Jira gates.
npx skills add https://github.com/Great-Gray-Group/devops-skills --skill pre-done
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
Validates that all required gates pass before a ticket or PR is marked Done, ensuring quality and preventing premature closures in software delivery.
Invoke /pre-done with a Jira key and optional service name to execute all gates before closing the ticket or merging the PR.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
byunghak-dableSummarize Git branch changes and post them as JIRA ticket comments.
luigiinredCompare the latest GitHub release with Jira's 'Merged' column to identify tickets needing 'Done' status.
shiroinockCoordinate TDD task orchestration from GitHub issue selection to PR completion.
vTRKADesign CI/CD release automation with quality gates and dry-run verification.
