skills.rest
nist0
nist0COMMUNITY
Explore all skills by this author →
GitHub

delivery

Define done criteria and enforce delivery quality gates with Python scripts.

Updated Apr 9, 2026
Search Tags:#release management#quality gates#delivery#CI#PR hygiene
One-click install
npx skills add https://github.com/nist0/CoDev --skill delivery-nist0
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: delivery
Source: https://github.com/nist0/CoDev/tree/main/.github/skills/delivery
Command: npx skills add https://github.com/nist0/CoDev --skill delivery-nist0

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of ensuring consistent delivery practices across the engineering lifecycle, from defining done criteria to post-release verification.

Core Features & Use Cases

  • Delivery Discipline: Provides a structured approach to delivery, including PR hygiene, CI quality gates, release readiness, and post-release verification.
  • Definition of Done: Offers a checklist for defining done criteria for features, bug fixes, or projects.
  • PR Discipline: Enforces best practices for pull request creation and review.
  • Quality Gates: Implements a set of quality checks to ensure code quality before merging.
  • Release Management: Offers a release readiness checklist and post-release verification steps.

Quick Start

Run the delivery skill with the command: delivery [feature-or-fix] [environment].

Frequently Asked Questions about delivery

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

FAQPage Schema
How do I enforce release management quality gates before merging code?▼

You can enforce release management quality gates by applying a structured checklist that validates CI checks, PR hygiene, and done criteria. This ensures code meets quality standards before merge and subsequent release readiness verification.

What is the best way to define done criteria for software engineering tasks?▼

The best way to define done criteria is using a structured delivery workflow checklist covering feature completion, bug fixes, and project requirements. This enforces consistent delivery discipline by verifying all done conditions are met before pull request creation.

How do I maintain pull request discipline across my engineering team?▼

Pull request discipline is maintained by enforcing best practices for PR creation and review within a structured delivery workflow. This includes integrating CI quality gates and verifying done criteria are satisfied before code review approval.

Do I need Python to run CI quality gates and release readiness checklists?▼

Yes, Python is required to execute the scripts that validate CI quality gates and release readiness checklists. The delivery workflow relies on Python to run validation scripts enforcing PR hygiene and post-release verification.

What steps are needed for post-release verification in a delivery workflow?▼

Post-release verification in a delivery workflow requires running validation scripts to confirm release stability after deployment. This structured step ensures the release readiness checklist was properly executed and production environments remain healthy.

Related Skills

Explore More Software Engineering Skills→
CyanAutomationCyanAutomation
1

ci-quality-gates

Reproduce CI quality gates locally to diagnose PR failures.

Community
Intermediate
GenEducationGenEducation

land-and-deploy

Merge a pull request, wait for CI and deployment, and verify production health with canary checks.

Official
Advanced
smarmen86smarmen86

ship

Automate branch merging, test execution, adversarial review, versioning, and pull request creation.

Community
Advanced
J03Fr0stJ03Fr0st

ci-cd-and-automation

Automate CI/CD pipeline setup with GitHub Actions and quality gates.

Community
Advanced