skills.rest
getdokan
getdokanOFFICIAL
Explore all skills by this author →
Website𝕏@dokantweetsGitHub

dokan-git

Standardize Git and GitHub workflows for the Dokan repository.

286|214|Updated Jan 31, 2017
Search Tags:#git#github#php#branching#coding-standards#wordpress#pull-requests
One-click install
npx skills add https://github.com/getdokan/dokan --skill dokan-git
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dokan-git
Source: https://github.com/getdokan/dokan/tree/main/.claude/skills/dokan-git
Command: npx skills add https://github.com/getdokan/dokan --skill dokan-git

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guidelines for Git and GitHub operations in the Dokan repository, ensuring consistent branches, PRs, and quality checks.

Core Features & Use Cases

  • Branch strategy: main development branch, release branches, and feature branches
  • PR checklist and templates: ensure coding standards, inline documentation, labels, changelog, and visual checks
  • Pre-commit checks and CI: PHPCS, PHPUnit, and Playwright tests to validate changes

Quick Start

Follow these guidelines when creating branches, making commits, and opening pull requests in the Dokan repository.

Frequently Asked Questions about dokan-git

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

FAQPage Schema
How do I structure Git branches when contributing to the Dokan plugin?▼

Dokan development requires feature branches to be created off the develop branch, while release branches must use release/x.y.z tags for versioning. This strategy ensures consistent integration across Dokan contributions.

What CI checks must a Dokan pull request pass before review?▼

Dokan pull requests must pass PHPCS for coding standards, PHPUnit for unit tests, and Playwright for E2E tests. These pre-commit and CI requirements validate changes before merging into the develop branch.

What should be included in a Dokan GitHub pull request checklist?▼

A Dokan PR checklist requires inline documentation, appropriate labels, changelog entries, and visual checks. Following these PR templates ensures WordPress coding standards compliance and consistent quality across Dokan contributions.

Does Dokan require specific WordPress coding standards for PHP commits?▼

Yes, Dokan enforces PHP coding standards through PHPCS pre-commit checks. All PHP commits must comply with these standards to pass CI requirements and qualify for pull request review.

When do I need to create a release branch in the Dokan workflow?▼

Release branches are needed when preparing a new Dokan plugin version for deployment. You must create branches using the release/x.y.z tag naming convention after development features are merged into the develop branch.

Related Skills

Explore More Software Engineering Skills→
gaupoitgaupoit
4

wordpress-development

Automates Docker-based WordPress setup, hardening, and verification workflows using WP-CLI and PHP 8.0+.

Community
Advanced
pacaplanpacaplan
30

release

Create release pull requests with semantic version bumps and changelog entries.

Community
Advanced
wpacademywpacademy
65

wp-plugin-review

Analyze WordPress plugins with PHPCS, PHPStan, and PHPUnit and generate a Markdown report.

Community
Advanced
getdokangetdokan
286

dokan-code-review

Review Dokan PHP code and pull requests for coding standards and security.

Official
Advanced