Skip to content

docs(wp-cli): add optional HOL Guard agent protection - #99

Closed
kantorcodes wants to merge 3 commits into
WordPress:trunkfrom
kantorcodes:feat/hol-guard-wpcli-safety
Closed

kantorcodes wants to merge 3 commits into
WordPress:trunkfrom
kantorcodes:feat/hol-guard-wpcli-safety

Conversation

@kantorcodes

Copy link
Copy Markdown

Summary

Adds an optional HOL Guard protection path to the existing wp-wpcli-and-ops skill for developers who run production-impacting WP-CLI operations through a supported local coding-agent harness.

The change directly installs and invokes HOL Guard at the agent harness boundary before WP-CLI writes, while preserving the WordPress-specific safeguards already in this skill: correct site targeting, backups, and WP-CLI dry-runs.

Scope

  • add the Guard-owned detect / install / run / doctor workflow to the maintained WP-CLI ops skill
  • fail closed on deny, review-required, error, or unavailable Guard states rather than suggesting a bypass
  • explicitly state that this is agent-side protection, not native WordPress or WP-CLI server interception
  • add one eval scenario covering the protected production wp search-replace workflow

No WordPress runtime, WP-CLI, or generic framework behavior is changed.

Validation

  • node eval/harness/run.mjs
  • python -m json.tool eval/scenarios/wpcli-hol-guard-protected-agent.json
  • git diff --check

The current checkout does not contain the scripts/format.sh referenced by CONTRIBUTING.md, so I am not claiming that script was run. New Markdown lines are wrapped to the documented 80-character target.

HOL Guard source: https://github.com/hashgraph-online/hol-guard

Affiliation: I maintain HOL Guard / Hashgraph Online. AI assistance was used to prepare this focused documentation/eval contribution; the submitted commands and boundary claims were checked against the maintained HOL Guard workflow and this repository's current contribution guidance.

@github-actions

Copy link
Copy Markdown
Contributor

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

Unlinked Accounts

The following contributors have not linked their GitHub and WordPress.org accounts: @kantorcodes.

Contributors, please read how to link your accounts to ensure your work is properly credited in WordPress releases.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Unlinked contributors: kantorcodes.


To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

@bgrgicak
bgrgicak requested a review from a team September 22, 2026 05:43
@bgrgicak

Copy link
Copy Markdown
Contributor

Thanks for contributing to Agent Skills @kantorcodes!
HOL Guard seems useful for a dev setup, especially for guarding production-impacting WP-CLI operations.

HOL Guard already provides its own agent skill, which users can adopt alongside the WordPress skills. So I will close this PR.

Also, in my opinion, we shouldn't favor or promote individual tools inside Agent Skills.

@bgrgicak bgrgicak closed this Oct 12, 2026
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.

2 participants