Menu
Unified Git workflow. Manages the entire task lifecycle: branch creation (sprint), atomic commits (git-os), and PR opening (pr-create).
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Unified development and design standards. Enforces code quality (complexity < 8), strict naming conventions, and the mandatory use of approved UI component libraries.
Unified codebase intelligence. Handles all questions about structure, logic, risk, and dependencies. Combines natural-language Q&A with deterministic lookups and pre-edit blast radius checks.
Use when asked to audit a module, check its health, or assess whether it should be refactored. Runs structural query, risk check, and test generation automatically.
Use when a dev is new to the project, asks for an overview, or wants to get oriented quickly. Fills graph gaps then runs a guided codebase interview.
Full PR review orchestrator. Use when asked to review a PR or check if it is ready to merge. Runs blast radius + drift check on changed files, then hands off to pr-review for comment triage and fixes. Do NOT use pr-review directly for full reviews — use this.
Enforces architecture boundaries defined in PLAN.md. Use when a PR crosses module/service boundaries, when the dev asks "are we following the architecture?", or as a scheduled architecture health check. Not for querying what a module does — use brownfield-chat for that.
This skill manages the complete lifecycle of a feature or fix. It ensures that every branch, commit, and PR follows the project's quality and automation standards.
sprint)When a dev provides a ticket and wants to start working:
type/name format (e.g., feat/user-auth).Bash(git checkout -b <branch_name>)git-os)When code is ready for an atomic commit:
type(scope?): Description (e.g., feat(auth): Add login endpoint).feat, fix, refactor, perf, docs, style, test, chore.npx --no-install commitlint would pass.pr-create)When the task is finished and ready for review:
npm run lint, format:check, test, and build.type(scope): Description.WED-142).### Ticket Link
---
### Description
---
### Steps to Test
---
### GIFs (if applicable)
---
Bash(git push origin <branch>)Bash(gh pr create --title "<title>" --body "<body>") using the template above.main or develop.codebase-intel risk score is > 80, require explicit confirmation before pushing.Bash for all git and gh operations.Read for package.json and .wednesday/config.json to check for project-specific automation.