wednesday-solutions/ai-agent-skills

# Module Audit Agent

## When to use
- "Audit this module"
- "Is it safe to refactor X?"
- "What is the health of this service?"
- "Should we rewrite X?"

## What to do

1. **In parallel:**
   - **brownfield-chat** — Read `dep-graph.json` and `summaries.json` for the target module. Report: what it does, its imports, what imports it, and any known conflicts.
   - **brownfield-fix** — Run `wednesday-skills score <module>` and `wednesday-skills blast <module>`. Report risk band and total dependent count.

# Dev Onboarding Agent

## When to use
- "I'm new to this project, where do I start?"
- "Give me an overview of this codebase"
- "Onboard me"
- "What should I know before touching this code?"

## What to do

1. **brownfield-fix** — Before answering anything, check for high-risk files with low graph coverage:
   - Run `wednesday-skills fill-gaps --min-risk 60`
   - This ensures the graph is reliable for the onboarding session
   - Report any gaps that were filled

# PR Review Agent

## When to use
- "Review this PR"
- "Is this PR ready to merge?"
- "Check this PR for issues"
- PR is open and review comments have been posted

## What to do

1. **triage-read** — Fetch all review comments via `gh pr view --comments`. Sort by impact: security → breaking → logic → performance → naming → style. Present the full categorised list to the dev.

2. **In parallel:**
   - **brownfield-fix** — Run `wednesday-skills score` and `wednesday-skills blast` on every file changed in the PR. Flag any file with risk > 60.

## When to use
- Dev asks "are we following the architecture?" or "is this a valid change?"
- PR touches files near module boundaries or service interfaces
- Weekly architecture health check
- Any cross-service import was just added

## When NOT to use
- "What does module X do?" → use **brownfield-chat**
- "What breaks if I change X?" → use **brownfield-chat**
- Graph coverage is low on a file → use **brownfield-fix (it fills gaps before editing)**
- No PLAN.md exists — drift requires machine-readable boundaries in PLAN.md

## What to do
1. Run `wednesday-skills drift` via Bash tool

# Codebase Intelligence Specialist

This skill provides a comprehensive understanding of the project's structure, intent, and risk. Use it for everything from high-level architecture questions to detailed impact analysis before editing code.

## When to use

### 1. Codebase Discovery & Q&A
- "What does `tokenService` do?" (Summaries)
- "Where is the payment logic located?" (Role/Path mapping)
- "Show me an overview of the architecture." (Stats & Entry points)
- "Who last touched this file?" (Git history)
- "Find circular dependencies or dead code." (Structural audit)

### 2. Risk Assessment (Before Editing)

# Deploy Checklist Skill

## Trigger

Load this skill when a dev is about to deploy or has just deployed:
- "We're deploying to production"
- "Pre-deploy check"
- "Post-deploy verification"
- "Run the deploy checklist"
- "Is it safe to deploy?"

**Do NOT use this skill for:** committing code (use `git-os`), creating a PR (use `pr-create`), or planning a project (use `greenfield`). This skill only applies at the deployment stage — code is already merged.

---

# Greenfield Planning Skill

## Trigger

Run once per project: `ws-skills plan`

Reads `BRIEF.md` from the project root (or prompts for one). Asks 5 clarifying questions before planning.

## Flow

```
Brief + Q&A
    ↓
Research agent (sequential)   ← domain landscape, ecosystem, hidden complexity

# PR Review — Gemini Fix Queue

## Trigger

Load this skill when a dev wants to **act on PR review comments**:
- "Fix the review comments"
- "Triage the PR feedback"
- "Apply fixes from the review"
- "@agent fix #1 #3"
- "@agent fix all"
- "What do I need to fix in this PR?"

Also triggered automatically by GitHub Actions when Gemini bot posts a PR review.

# Standards Kit (Dev & Design)

This kit ensures every line of code and every UI element follows Wednesday Solutions' high-quality standards.

## 🚦 Decision Flow

```
1. DO NOT create custom UI components. 
   Check references/VISUALS.md for approved libraries.
2. Keep Cyclomatic Complexity < 8. 
   Check references/LOGIC.md for refactoring strategies.
3. Use PascalCase for UI/Types and camelCase for Logic.
4. Follow strict Import Ordering (React -> Next -> State -> UI -> Alias -> etc.).
```

# Wednesday Git Workflow (GIT-OS)

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.

## Lifecycle Phases

### 1. Starting a Task (`sprint`)
When a dev provides a ticket and wants to start working:
- **Action**: Create a branch following the `type/name` format (e.g., `feat/user-auth`).
- **Rule**: Max 40 characters, kebab-case, no ticket numbers in the branch name.
- **Tool**: `Bash(git checkout -b <branch_name>)`

### 2. Committing Changes (`git-os`)
When code is ready for an atomic commit: