Per Søderlind soderlind

Keep WordPress core patched automatically with Dependabot

A tiny Dependabot config that watches WordPress core (installed via Composer as roots/wordpress)_A and opens a pull request whenever a patch release ships — which is how WordPress delivers security fixes (e.g. 6.8.7 → 6.8.8).

Minor and major releases (e.g. 6.8 → 6.9) are ignored on purpose — those are plugin/theme compatibility decisions you make by hand.

Below is a complete build guide for a dedicated Grilling Agent in Copilot Studio. It adapts Matt Pocock’s original grilling skill to Copilot Studio’s capabilities.

You should really check out Matt Pocock’s AI skills at https://www.aihero.dev/skills

The main adaptation replaces sub-agent delegation with Copilot Studio knowledge and research tools, adds safeguards, and produces a structured decision record.

1. Create the skill package

Create this folder:

Folkeeventyr-importør for WordPress

import-folkeeventyr.sh henter eventyr fra Nasjonalbibliotekets API, lagrer hvert eventyr som en JSON-fil og kan importere dem som WordPress-sider ved hjelp av WP-CLI.

Teksten hentes fra digitaliserte bøker via IIIF-manifest og ALTO-OCR-XML. Standardkilden er Eventyrbok for børn (1908) av Asbjørnsen og Moe, som er i det fri og tilgjengelig fra hele verden. En annen bok kan velges med --nb-item-id.

Copy options from one subsite to another

# Read the RAW option value from the source site (bypasses the masking filter)
wp --path=/path/to/SOURCE option list --search='EXACT_OPTION_NAME' --field=option_value \
  | wp --path=/path/to/TARGET option update EXACT_OPTION_NAME

# Verify on the target with option list (NOT option get, which also runs the mask filter)
wp --path=/path/to/TARGET option list --search='EXACT_OPTION_NAME' --field=option_value

Bayesian rating with compatibility and maintenance adjustments

The adjusted extension score ranks WordPress themes and plugins using three signals:

$$ \text{Adjusted score} = 0.70B + 0.20(5W) + 0.10(5M) $$

Where:

Below are complete WordPress-style examples that extend your snippets with basic WP_Error handling, sanitization, escaping, and flexible handling for common return shapes.

I’m assuming:

wp_ai_client_prompt( $prompt ) returns a prompt object.
generate_text() returns a string or WP_Error.
generate_image() returns an image URL, attachment ID, array like ['url' => ...], or WP_Error.
convert_text_to_speech() returns an audio URL, attachment ID, array like ['url' => ...], or WP_Error.

Benchmark report: WordPress ticket #64863

Branch: benchmark/64863
PR: #11257 — Eliminate switch_to_blog() from multisite option/post functions
Environment: PHP 8.3.30 · WordPress 7.0-beta5-61991-src · MySQL 8.4 · Docker (linux/amd64 via Rosetta on arm64)
Method: 200 iterations × 3 runs per function, median taken. Cold = cache flushed before each run. Warm = cache intact.

Cold cache

How I do vibe coding in 3 steps (plus a Step 0)

Start with domain expertise
Vibe coding works best when you have enough domain expertise to set direction, ask precise questions, and validate the output.
Jam with an AI chat — then “lock in” a single strong prompt
I start by brainstorming with ChatGPT (or another chat model): goals, constraints, edge cases, and what “done” looks like.
I end by asking the AI to produce one clean prompt that includes:
- problem statement + scope (what to do / not do)

assumptions and constraints

⠀⠀⠀⠀⠀⠀⣀⣤⣶⡶⢛⠟⡿⠻⢻⢿⢶⢦⣄⡀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀
⠀⠀⠀⢀⣠⡾⡫⢊⠌⡐⢡⠊⢰⠁⡎⠘⡄⢢⠙⡛⡷⢤⡀⠀⠀⠀⠀⠀⠀⠀
⠀⠀⢠⢪⢋⡞⢠⠃⡜⠀⠎⠀⠉⠀⠃⠀⠃⠀⠃⠙⠘⠊⢻⠦⠀⠀⠀⠀⠀⠀
⠀⠀⢇⡇⡜⠀⠜⠀⠁⠀⢀⠔⠉⠉⠑⠄⠀⠀⡰⠊⠉⠑⡄⡇⠀⠀⠀⠀⠀⠀
⠀⠀⡸⠧⠄⠀⠀⠀⠀⠀⠘⡀⠾⠀⠀⣸⠀⠀⢧⠀⠛⠀⠌⡇⠀⠀⠀⠀⠀⠀
⠀⠘⡇⠀⠀⠀⠀⠀⠀⠀⠀⠙⠒⠒⠚⠁⠈⠉⠲⡍⠒⠈⠀⡇⠀⠀⠀⠀⠀⠀
⠀⠀⠈⠲⣆⠀⠀⠀⠀⠀⠀⠀⠀⣠⠖⠉⡹⠤⠶⠁⠀⠀⠀⠈⢦⠀⠀⠀⠀⠀
⠀⠀⠀⠀⠈⣦⡀⠀⠀⠀⠀⠧⣴⠁⠀⠘⠓⢲⣄⣀⣀⣀⡤⠔⠃⠀⠀⠀⠀⠀
⠀⠀⠀⠀⣜⠀⠈⠓⠦⢄⣀⣀⣸⠀⠀⠀⠀⠁⢈⢇⣼⡁⠀⠀⠀⠀⠀⠀⠀⠀

	# ── Oh My Zsh ────────────────────────────────────────────────
	export ZSH="$HOME/.oh-my-zsh"
	IS_VSCODE=$([[ "$TERM_PROGRAM" == "vscode" ]] && echo true \|\| echo false)

	if [[ "$IS_VSCODE" == "true" ]]; then
	ZSH_THEME=""
	# Reduce title/prompt noise before Oh My Zsh initializes.
	DISABLE_AUTO_TITLE=true
	COMPLETION_WAITING_DOTS=false
	DISABLE_UNTRACKED_FILES_DIRTY=true