jparkerweb

Perform a standards-based code review on a GitHub Pull Request, then post the findings as inline review comments and mark the PR as 'Requested changes'. Reads all of the agents files that exist in the repository under review (AGENTS.md, .agents-docs/, CLAUDE.md on the PR's base branch) — the repo's full documented standards, not just any agents files the PR happens to change — checks the diff against them plus general best practices, and gates every write behind explicit approval. Use this skill whenever the user wants to code-review a PR, review a pull request, check a PR against standards, request changes on a PR, or gives you a GitHub PR link and asks for a review. Also triggers on: 'review this PR', 'code review', 'review PR', 'check this pull request', 'request changes', 'review against our standards', or a bare github.com/.../pull/<n> URL with review intent. This is a review-only skill — it never approves, merges, closes, or pushes code.

Run the encrypted, password-protected repository sync workflow for this project. The real instructions are stored encrypted at rest and are only revealed in-session after you supply the correct password. Invoke explicitly with /sync-repo.

Guide the user through containerizing and serving a simple website or documentation folder with Docker — inspects the project to detect what to serve (ready-to-serve static HTML, a buildable site that emits static output, or a raw markdown/docs folder that needs rendering), generates a Dockerfile, .dockerignore, docker-compose.yml, helper run/build commands, and a 'Running with Docker' README section, then offers to build and smoke-test the container and publish the image to Docker Hub or GHCR. Uses nginx:alpine for static content and a multi-stage build when the site must be generated. Only invoke when the user explicitly types /ai-assist-dockerize-website. Never auto-trigger from general conversation about Docker, containers, websites, or Dockerfiles.

Validate and fix the CHANGELOG.md version number before opening a PR, commiting, or pushing changes, and keep package.json's version aligned with it. Reads main branch to determine the current latest version, classifies changes on the current branch, and proposes the correct next semver. Use this skill when the user mentions changelog, version number, preparing a PR, release version, semver check, or says 'check the changelog', 'what version should this be', 'prepare for PR', or 'fix the version'. Also use proactively when you notice a CHANGELOG entry that may have an incorrect version number.

Bulk-update outdated npm dependencies across one or more package.json files. Finds every package.json in the current working directory (recursively, skipping node_modules), runs npm outdated, bumps each outdated dependency to its 'wanted' version prefixed with ^, then runs npm install. Use whenever the user wants to update npm dependencies, bump packages to their wanted versions, refresh package.json versions, or run npm outdated and apply the results — including across a monorepo or multiple projects at once. Triggers on: update npm packages, update dependencies, bump npm versions, npm outdated, refresh package.json.

Reverse-engineer a website's visual design system from a URL and produce a fully spec-compliant DESIGN.md file (https://github.com/google-labs-code/design.md). The output includes both machine-readable YAML design tokens (colors, typography, spacing, rounded corners, components) and human-readable markdown rationale sections (Overview, Colors, Typography, Layout, Elevation & Depth, Shapes, Components, Do's and Don'ts). Use this skill whenever the user wants to generate a DESIGN.md, create a design system file from a website, capture a site's visual identity, extract design tokens, build a design spec from a URL, clone a site's look and feel, or scaffold a DESIGN.md from scratch. Also triggers on: 'design system from URL', 'generate DESIGN.md', 'extract colors from site', 'what are this site's design tokens', 'capture design from website'.

Deep research and analysis workflow for codebases, technologies, domains, ideas, or data. Produces structured documentation with analytical frameworks, confidence-graded findings, and cited sources. Use when evaluating technologies, investigating domains, assessing feasibility, or analyzing codebases in depth.

Stage and commit changes using the team's standard commit message format. Only invoke when the user explicitly types /ai-assist-git-commit. Never auto-trigger from general conversation about commits or git.

Build a static HTML site at docs/ from the wiki/ directory, styled per DESIGN.md. Wipes and regenerates docs/ on every run. Use when the user asks to publish, build the site, regenerate HTML, or update docs/.

Convert every PDF in source/ into an AI-readable markdown file alongside it, then delete the original PDF. Run once after dropping new PDFs into source/ so that wiki-sync can ingest them.

Answer a question about the HOA / townhome using the wiki/ directory as authoritative context. If the user invoked /ask with no arguments, ask them what they want to know first. Always cite the wiki page and original source section.

Build or incrementally update the HOA wiki from documents in source/. Detects changed source files via SHA-256 hashes and only re-ingests what changed. Run after adding, editing, or removing files in source/.

Regenerate eQuill Labs content from GitHub with optional guidance. Stops for human review before build and before commit.

List, add, edit, or remove project categories (library, plugin, cli, service, app, demo) in the eQuill Labs site. Use whenever the user wants to review current categories, introduce a new one, rename an existing one, delete one, or change how the auto-derivation rules in `scripts/curate.ts` map GitHub topics to a category. Trigger on phrases like 'add a new category', 'rename the cli category', 'what categories do we have', 'remove the demo category', 'change how X is categorized', 'project type', or any mention of modifying the Type filter on the projects page.

Cut a new semver release — updates CHANGELOG.md, commits, tags, and pushes to trigger the GoReleaser CI pipeline. Use this skill whenever the user says "release", "cut a release", "bump version", "tag a release", "ship it", or wants to publish a new version. Also use when the user types "/shrinkray-release".

Audit and update all project documentation (README, AGENTS.md, and .agents-docs/ files) to match the current codebase. Use when the user says "update docs", "sync docs", "audit docs", "docs are stale", "refresh documentation", or after significant code changes. Also use when the user types "/shrinkray-update-docs".

Run npm install and npm audit to fix vulnerabilities in both root and example directories

Build/publish The Cottage Garden Companion site by mirroring ./src into ./docs (the GitHub Pages publish directory). Use this whenever the user wants to build the site, (re)generate or refresh ./docs, publish or deploy the pages, prepare for GitHub Pages, or stage the HTML tools for release — even when they just say "build it", "rebuild docs", or "update the published site". It runs a zero-dependency Node script and is the single place any future build step (minification, asset processing, sitemap) gets added.