Skip to content

docs: document custom commands support#52

Open
lbajsarowicz wants to merge 1 commit intowardenenv:mainfrom
lbajsarowicz:docs/custom-commands
Open

docs: document custom commands support#52
lbajsarowicz wants to merge 1 commit intowardenenv:mainfrom
lbajsarowicz:docs/custom-commands

Conversation

@lbajsarowicz
Copy link
Contributor

Summary

  • Add a Custom Commands section to the Customizing An Environment page
  • Document two locations: <project>/.warden/commands/ (project-level) and ~/.warden/commands/ (global)
  • Explain resolution order: project → global → built-in
  • Each command needs a <name>.cmd (script) and <name>.help (for warden help listing)
  • Include a practical example (cache flush command)
  • Link to the Magento 2 template as a real-world reference

This feature has been available since v0.2.0 (#172) but was never documented.

⭐ Support my work

Do you like the fix? Remember to react with "👍🏻" to get it merged faster,
Then Sponsor me on Github so I can spend more time on fixing issues like this one.

Learn more at https://github.com/sponsors/lbajsarowicz

Add Custom Commands section to the customizing page explaining
how to create project-level and global custom commands using
.cmd and .help files, including resolution order, example, and
link to the Magento 2 template as a real-world reference.
lbajsarowicz added a commit to lbajsarowicz/ai-skills that referenced this pull request Mar 22, 2026
Add Custom Commands section to commands.md explaining project-level
and global custom commands via .cmd/.help files, resolution order,
and link to Magento 2 template as real-world example.

Companion to wardenenv/docs#52.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant