fls

Look at the code review comments on the PR and address all issues.

Read through all the changes made since the last commit so you understand what I'm working on.

Make a Git commit.

Look for all comments that mention @claude across the whole code base.

Use mermaid. Create a file that shows the dependencies between different apps defined in this project.

Create a github issue

Create a new placeholder page for a page:

run `git rebase main` and fix all the merge conflicts.

Perform a security review of the current changes:

To do this:

Execute a frontend QA test plan using Playwright MCP

Do the final cleanup for the current worktree

1. Read the plan file

Improve the idea by doing research and making suggestions

Create an implementation plan based on a spec file

Create a specification based on an idea

Check that the spec makes sense

Make a worktree for the current spec

Implement the functionality here using a TDD approach.

Perform threat modeling for: $ARGUMENTS

Use this agent when the user wants a review of recent code changes. This includes reviewing all changes in a branch compared to main, reviewing specific commits, or reviewing uncommitted/staged changes. Examples: - User: "Review my changes" Assistant: "I'll use the code-reviewer agent to review your recent code changes." [Launches code-reviewer agent via Task tool] - User: "Can you review the last 3 commits?" Assistant: "I'll launch the code-reviewer agent to review those commits." [Launches code-reviewer agent via Task tool] - User: "Review the changes on this branch" Assistant: "I'll use the code-reviewer agent to review all changes on this branch compared to main." [Launches code-reviewer agent via Task tool] - User: "I just finished implementing the deadline feature, can you take a look?" Assistant: "I'll launch the code-reviewer agent to review your recent changes." [Launches code-reviewer agent via Task tool] - User: "Check my uncommitted changes before I commit\" Assistant: "I'll use the code-reviewer agent to review your uncommitted changes." [Launches code-reviewer agent via Task tool]

Use this agent when the user needs test data created in the development database for manual QA testing. This includes creating users, courses, cohorts, progress records, or any other domain objects needed to test the application in a browser. The agent should be used whenever the user asks for test data, sample data, demo data, or mentions needing specific scenarios set up for testing. Examples: - user: "I need 5 students enrolled in a course with some progress" assistant: "I'll use the qa-data-factory agent to create the test data using factory_boy factories." <commentary>The user needs test data for QA. Use the Agent tool to launch the qa-data-factory agent to create the data.</commentary> - user: "Set up a cohort with an educator and 10 students" assistant: "Let me use the qa-data-factory agent to set up that cohort scenario." <commentary>The user needs a specific test scenario. Use the Agent tool to launch the qa-data-factory agent.</commentary> - user: "I need a student who has completed half of a course" assistant: "I'll use the qa-data-factory agent to create a student with partial course progress." <commentary>The user needs a specific data state for QA testing. Use the Agent tool to launch the qa-data-factory agent.</commentary> - user: "Create a management command that generates a full QA dataset" assistant: "Let me use the qa-data-factory agent to build that management command in the qa_helpers app." <commentary>The user wants a reusable data generation tool. Use the Agent tool to launch the qa-data-factory agent.</commentary>

Configure Django admin with Unfold and SiteAwareModelAdmin. Use when creating/modifying admin classes, working with inlines, or when the user mentions admin interface.

How to use Alpine.js for client-side interactivity. Use when adding interactive behaviour to templates such as toggles, dropdowns, modals, expand/collapse, dismissible elements, or any client-side state.

FreedomLS brand identity, visual system, and voice guidelines. Use whenever building UI, writing copy, creating templates, choosing colours/fonts, or making any design or communication decision for the FreedomLS project. This includes: HTML/CSS/Tailwind styling, Django templates, README content, documentation, error messages, marketing pages, emails, social posts, and component libraries. If you are writing code or content that a human will see in a FreedomLS context, consult this skill.

Create or modify branded HTML+text multipart emails for django-allauth flows. Use when working with email templates, email styling, or notification emails.

Create test data with factory_boy and SiteAwareFactory. Use when creating factories, writing test data setup, or when the user mentions factory_boy or test data.

Frontend styling with Tailwind including applying classes to templates and components, creating UI elements, reviewing markup, modifying component classes, and building Tailwind.

Reference this skill whenever you need to understand the worktree setup for this project.

Use when making HTMX interactions

Use this skill when making use of any icons in any part of the frontend.

Work with markdown content system, MarkdownContent models, and cotton components in markdown. Use when working with content models or adding markdown components.

Work with Django Sites framework, SiteAwareModel, and site isolation. Use when creating/modifying models, working with multi-tenancy, or when site context is involved.

Write Playwright E2E tests for user flows and browser interactions. Use when testing HTMX, user journeys, or when the user mentions E2E, Playwright, or browser testing.

Use when completing tasks, implementing major features, or before making commits.

Create or edit Django templates with cotton components, template partials, and proper Tailwind usage. Use when creating/editing HTML templates, adding components, or when the user mentions templates, UI, or frontend work.

Write pytest tests. Use when implementing features, fixing bugs, or when the user mentions testing, TDD, or pytest

Use Playwright MCP to interactively browse, inspect, and interact with the running dev site. Use when the user asks you to look at a page, check how something looks, click through a flow, fill in forms, or debug UI issues in the browser.

4 hooks across 2 events