fivetwofive-cw

Best practices for committing completed work on the FiveTwoFive WordPress site. Use this skill when the user says "commit", "let's commit", "commit these changes", "I'm ready to commit", or "commit and push". Covers rebuilding theme assets, staging the right files (the deny-all `.gitignore` silently ignores new files), a WordPress-specific hostile-read checklist, writing a good commit message, and opening a PR. Trigger any time work is complete and ready to be committed — don't wait for the user to ask about best practices explicitly.

Address and fix GitHub pull request review comments on the FiveTwoFive WordPress site (incl. Codex bot reviews). Use whenever the user shares a PR URL or says "address the comments", "review the PR", "fix the feedback", "resolve the review", "handle the Codex comments", "address any open comments", or pastes a PR URL with "fix this PR" / "take care of the comments". Handles the full loop: fetch comments → verify each against code → fix or rebut → rebuild assets → commit + push → reply + resolve each thread → recheck for the reviewer's follow-up.

Creates a properly-named git branch before starting any new work on the FiveTwoFive WordPress site. Use this skill at the start of every coding session, feature, bug fix, or task. Trigger whenever the user mentions starting something new, working on an issue, fixing a bug, or any time work is about to begin and no feature branch has been created yet. If the user jumps straight into making changes without creating a branch first, pause and run this skill before proceeding. Phrases like "let's work on X", "can you fix Y", "start on issue #Z", or "I want to add A" are all signals to run this skill first.

Opens a GitHub pull request for the FiveTwoFive WordPress site with a structured, reviewable body. Use this skill whenever the user says "open a PR", "create the PR", "push and open a PR", "ship it", or anytime work is committed and pushed to a working branch but the PR hasn't been opened yet. Also invoke automatically as the final step of `/ftf-commit-feature` after a successful push. Produces a PR description in the standard four-section shape (Summary / Decisions baked in / Test plan / Follow-ups) with checkbox-formatted verification steps.

Returns the local FiveTwoFive repo to a verifiably clean state on the latest `master` before starting the next task. Use after a PR is merged, when switching context between tasks, or any time you want to confirm `master` is up to date and stale local branches are cleaned up. Trigger phrases include "sync master", "clean up", "back to master", "fresh start", "start the next thing", "we just deployed", "PR is merged what's next", or any signal that the previous unit of work is finished and a new one is about to begin. This skill does NOT create a branch — chain to `/ftf-new-branch` when ready to start work.