malikad778

Static analysis for WordPress hooks. Detect orphaned listeners, unheard hooks, and typos in actions and filters without running WordPress. Faster, safer WP development.

10
0
100% credibility
Found Mar 03, 2026 at 10 stars -- GitGems finds repos before they trend. Get early access to the next one.
Sign Up Free
AI Analysis
PHP
AI Summary

A scanning tool that checks WordPress plugins and themes for mismatched or broken hook connections to prevent silent failures in production.

How It Works

1
🔍 Spot the Problem

You're fixing a mysterious issue in your WordPress plugin where a feature quietly stopped working, and you hear about a handy checker that finds hidden broken connections.

2
📦 Grab the Checker

You quickly add this free tool to your WordPress development setup so it's ready to use anytime.

3
📁 Pick Your Folder

Choose the folder with your plugin or site files, like the plugins directory, to examine.

4
▶️ Start the Scan

Hit go, and in seconds it reviews every file to spot unmatched connections between plugin actions.

5
📋 Review the Report

See a friendly list of issues like unused listeners or silent hooks, with easy fix tips.

6
🔧 Apply the Fixes

Make the suggested changes to reconnect everything properly in your code.

Perfect Connections

Scan once more to celebrate—no issues left, ensuring your site runs smoothly without surprises.

Sign up to see the full architecture

5 more

Sign Up Free

Star Growth

See how this repo grew from 10 to 10 stars Sign Up Free
Repurpose This Repo

Repurpose is a Pro feature

Generate ready-to-use prompts for X threads, LinkedIn posts, blog posts, YouTube scripts, and more -- with full repo context baked in.

Unlock Repurpose
AI-Generated Review

What is wp-hook-check?

wp-hook-check is a PHP static analysis tool for WordPress hooks that scans your codebase to detect orphaned listeners, unheard hooks, and name typos in actions and filters—without booting up WordPress. It maps every add_action, do_action, add_filter, and apply_filters call across PHP files, flagging mismatches that silently break features in production. Run it via Composer CLI like `vendor/bin/wp-hook-audit audit .` or WP-CLI with `wp hook-check ./plugins/my-plugin` for fast, zero-runtime checks.

Why is it gaining traction?

Unlike dynamic linters or WP runtime debuggers, it delivers github static code analysis results in seconds, with GitHub annotations for PRs, JSON exports, and CI-friendly exit codes via actions. Typo detection spots near-matches like "my_hook_before" vs "my_hookbefor", and config files let you ignore WP core prefixes or dynamics. Developers love the dump mode for exploring hook maps in unfamiliar repos, akin to static analysis tools for Java or C++ but tailored for WP.

Who should use this?

WordPress plugin maintainers scanning for refactors that break extensibility, theme devs auditing cross-plugin hook conflicts, or teams adding it to GitHub Actions pipelines for static analysis of code before merges. Ideal for mid-sized WP agencies tired of prod outages from renamed hooks.

Verdict

Grab it for dev dependency if you build WP plugins—solid docs, WP-CLI support, and MIT license make it plug-and-play despite 10 stars and 1.0% credibility score signaling early maturity. Test on a real project first; pair with broader static analysis tools for full coverage.

(198 words)

Sign up to read the full AI review Sign Up Free

Similar repos coming soon.