PHPackages                             wordrobe/cli - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [CLI & Console](/categories/cli)
4. /
5. wordrobe/cli

ActiveLibrary[CLI & Console](/categories/cli)

wordrobe/cli
============

Boosting development CLI for Wordpress

v1.0.6(5y ago)26.4k21MITPHPPHP ^7.2

Since Jul 17Pushed 5y ago1 watchersCompare

[ Source](https://github.com/wordrobe/cli)[ Packagist](https://packagist.org/packages/wordrobe/cli)[ RSS](/packages/wordrobe-cli/feed)WikiDiscussions master Synced 2mo ago

READMEChangelog (1)Dependencies (5)Versions (18)Used By (1)

[![](https://camo.githubusercontent.com/5803818e61779730b5ef27704a636cbe2e1c90cf877ef23d3666a57a945e40a5/68747470733a2f2f7777772e666961642e6f6e652f6d656469612f776f7264726f62652f62616e6e65722d636c692e6a7067)](https://camo.githubusercontent.com/5803818e61779730b5ef27704a636cbe2e1c90cf877ef23d3666a57a945e40a5/68747470733a2f2f7777772e666961642e6f6e652f6d656469612f776f7264726f62652f62616e6e65722d636c692e6a7067)

*Wordrobe* is a *Wordpress* development boosting tool that combines the quickness of automated processes with the solidity of a structured workflow.

By taking charge of the most common operations concerning *Wordpress* themes development and by providing a well organized development model, it allows you to save time and to produce a better quality code with an eye towards modularity and maintainability.

Requirements
------------

[](#requirements)

- *[Composer](https://getcomposer.org)* >= 1.8
- PHP (CLI) >= 7.2

Installation
------------

[](#installation)

To install *Wordrobe* just run the following command at the root of your project:

```
composer require wordrobe/cli

```

Once installed, *Wordrobe* requires a simple initial configuration to fit in your project's structure so it can write and handle files at correct paths.

By running

```
vendor/bin/wordrobe setup

```

a setup wizard will start and a *wordrobe.json* file will be automatically created at your project's root. It will look like this:

```
{
  "themes-path": "your/path/to/themes",
  "themes": {}
}

```

💡 In a standard *Wordpress* installation, "themes-path" will be "wp-content/themes".

Usage
-----

[](#usage)

*Wordrobe* exposes all its power of adding features to your *Wordpress* based application by the simplest way ever: just run the following command and enjoy the wizard:

```
vendor/bin/wordrobe add:[feature]

```

Check the complete [commands list](./doc/COMMANDS.md) to discover all supported features.

### Fundamentals

[](#fundamentals)

#### Adding a new theme

[](#adding-a-new-theme)

One of the most basic but most important operations you deal with when you start a new *Wordpress* project, is the creation of a brand new theme. At this stage, many doubts about structure and files organization usually arise, specially when focus about code modularity and maintainability is required.

*Wordrobe* offers an optimized theme's file system that helps you to keep your code scoped and well organized, encouraging front-end/back-end separation, integration and reusability. For more information, check theme's [in-depth documentation](./doc/THEME.md).

To create a new theme, simply run the command below and follow the wizard:

```
vendor/bin/wordrobe add:theme

```

💡 *Wordrobe* supports multi-theme development, so if more than one theme will be added to your project, you will be asked which theme you want to deal with each time you'll run the ***add*** command.

#### Adding a page template

[](#adding-a-page-template)

Page templates are one of the most commonly used ways to make an association between specific contents and layout. To let *Wordrobe* to create one for you, just run the following command:

```
vendor/bin/wordrobe add:page

```

The page template creation process let us to observe the first pillar of *Wordrobe* architecture: the ***controller/view pattern*** implementation. It's entrusted to *[Twig](https://twig.symfony.com)* through the use of *Timber* plugin by *[Upstatement](https://www.upstatement.com)* and allows a perfect separation between front-end and back-end development.

For more information, check the ***controller/view pattern***'s [in-depth documentation](./doc/PATTERN.md).

#### Adding a custom post-type

[](#adding-a-custom-post-type)

Another common operation in *Wordpress* theme development is the creation of custom post-types, aimed to handle project-specif content types. By the following command, *Wordrobe* comes in support for this goal too:

```
vendor/bin/wordrobe add:post-type

```

Along with the post-type registration code and the ***controller/view pattern*** implementation, the command above provides the scaffolding that allows *Wordrobe* to carry out its own architecture through the introduction of its second pillar: the ***entity/repository/dto framework***.

It's inspired by *[Doctrine](https://www.doctrine-project.org)* and you can learn more about it by reading its [in-depth documentation](./doc/FRAMEWORK.md).

### More?

[](#more)

Check the [example](./example) for more details and information about *Wordrobe* usage.

###  Health Score

33

—

LowBetter than 75% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity23

Limited adoption so far

Community11

Small or concentrated contributor base

Maturity66

Established project with proven stability

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~58 days

Recently: every ~172 days

Total

17

Last Release

1929d ago

Major Versions

v0.1.4 → v1.0.0-beta2019-01-08

PHP version history (2 changes)v0.0.1PHP ^7.1

v1.0.3PHP ^7.2

### Community

Maintainers

![](https://www.gravatar.com/avatar/1562229032294c4e5aac397a136b99ecc8016196646c9aebd6ff50af50839e6d?d=identicon)[Fiad](/maintainers/Fiad)

---

Top Contributors

[![maurothewolf](https://avatars.githubusercontent.com/u/12728609?v=4)](https://github.com/maurothewolf "maurothewolf (2 commits)")

###  Code Quality

Static AnalysisPHPStan

Type Coverage Yes

### Embed Badge

![Health badge](/badges/wordrobe-cli/health.svg)

```
[![Health](https://phpackages.com/badges/wordrobe-cli/health.svg)](https://phpackages.com/packages/wordrobe-cli)
```

###  Alternatives

[humbug/php-scoper

Prefixes all PHP namespaces in a file or directory.

7963.0M35](/packages/humbug-php-scoper)[illuminate/console

The Illuminate Console package.

12944.1M5.1k](/packages/illuminate-console)[matthiasnoback/symfony-console-form

Use Symfony forms for Console command input

368264.8k8](/packages/matthiasnoback-symfony-console-form)[wp-cli/package-command

Lists, installs, and removes WP-CLI packages.

187.6M9](/packages/wp-cli-package-command)[shel/neos-terminal

Neos CMS Ui terminal for running Eel expressions and other commands

1441.3k](/packages/shel-neos-terminal)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)