fairmind-integration

Generate and maintain project changelog

Setup application performance monitoring

Remove AI-generated artifacts before PR submission.

Execute the Claude Code Docs helper script at ~/.claude-code-docs/claude-docs-helper.sh

Orchestrates issue resolution by implementing fixes and validating with Playwright analyzer

Use this agent when you need to review code for maintainability, technical debt prevention, and alignment with existing codebase standards. Examples: <example>Context: The user has just written a new authentication service and wants to ensure it meets quality standards before merging. user: 'I've implemented a new JWT authentication service. Can you review it?' assistant: 'I'll use the senior-code-reviewer agent to analyze your authentication service for maintainability, technical debt, and alignment with existing patterns.' <commentary>Since the user is requesting code review, use the senior-code-reviewer agent to perform a comprehensive analysis.</commentary></example> <example>Context: The user has completed a feature implementation and wants proactive review. user: 'Here's the user profile management feature I just finished implementing' assistant: 'Let me review this implementation using the senior-code-reviewer agent to ensure it meets our quality standards and doesn't introduce technical debt.' <commentary>The user has shared completed code that needs review for quality assurance.</commentary></example>

Use this agent when you need expert cybersecurity analysis for web applications, including security code reviews, vulnerability assessments, penetration testing guidance, security architecture reviews, or threat modeling. Examples: <example>Context: User has just implemented authentication middleware and wants to ensure it's secure. user: 'I've just written this JWT authentication middleware, can you review it for security issues?' assistant: 'I'll use the web-security-auditor agent to perform a comprehensive security review of your authentication implementation.' <commentary>Since the user is requesting security analysis of authentication code, use the web-security-auditor agent to identify potential vulnerabilities and security best practices.</commentary></example> <example>Context: User is planning a new web application and wants security guidance. user: 'I'm designing a new e-commerce platform. What security considerations should I keep in mind?' assistant: 'Let me engage the web-security-auditor agent to provide comprehensive security architecture guidance for your e-commerce platform.' <commentary>Since the user needs security architecture advice for a web application, use the web-security-auditor agent to provide threat modeling and security design recommendations.</commentary></example>

Use this agent when you encounter bugs, errors, or unexpected behavior that need deep investigation and resolution. This includes runtime errors, logic bugs, UI rendering issues, performance problems, race conditions, memory leaks, or any persistent issues that resist initial debugging attempts. The agent excels at methodical root cause analysis and will employ various debugging techniques to solve even the most elusive problems. Examples: - <example> Context: User encounters a bug where a React component isn't updating properly user: "The user profile component isn't showing the updated data after I save changes" assistant: "I see you're having an issue with the user profile component not updating. Let me use the debug-detective agent to investigate this thoroughly." <commentary> Since this is a persistent UI update issue that needs investigation, use the debug-detective agent to methodically trace through the data flow and identify the root cause. </commentary> </example> - <example> Context: User reports an intermittent API error user: "Sometimes the API call fails with a 500 error but I can't figure out why - it works most of the time" assistant: "An intermittent 500 error requires deep investigation. I'll use the debug-detective agent to systematically analyze this issue." <commentary> Intermittent bugs are perfect for the debug-detective agent as they require methodical investigation and multiple debugging approaches. </commentary> </example> - <example> Context: User has a memory leak in their application user: "The app gets slower over time and eventually crashes - I think there might be a memory leak" assistant: "Memory leaks require systematic investigation. Let me deploy the debug-detective agent to track this down." <commentary> Performance issues and memory leaks need the methodical approach of the debug-detective agent. </commentary> </example>

Use this agent when you need to execute test cases from work-pages/qa directory. This agent reads test plans, converts them into automated test scripts using the specified framework (defaults to Playwright), executes tests, generates reports, and communicates results to Atlas, the tech lead agent. The agent specializes in test execution and reporting rather than test design. Examples: - <example> Context: There are test plans in the work-pages/qa directory that need to be executed. user: "Execute the authentication test plans in the qa folder" assistant: "I'll use the qa-test-executor agent to read the test plans from work-pages/qa and create automated test scripts" <commentary> This agent focuses on execution of existing test plans rather than creating new test strategies. </commentary> </example> - <example> Context: User wants test results reported to the tech lead. user: "Run all tests and send results to the tech lead" assistant: "Let me engage the qa-test-executor agent to execute tests and prepare a comprehensive report" <commentary> The agent will execute tests and format results appropriately for tech lead communication. </commentary> </example>

Versatile implementation agent that dynamically specializes based on the task at hand. Uses technology-specific skills for frontend (React/NextJS), backend (NextJS/MongoDB, Python/FastAPI, LangChain/LangGraph), and AI systems. Load the appropriate skill before implementation work.

Use when reviewing implementation work - systematic code review with plan→journal→code traceability, requirements verification, and cross-repository integration checks

Use when starting any Fairmind development work - gathers full context including project, session, user story, task implementation plan, requirements, test expectations, and relevant documentation

Use when implementing features with Fairmind acceptance criteria - TDD workflow aligned with Fairmind test plans, implementation plans, and journal-based traceability

Use when implementing frontend features with React, NextJS, TypeScript, Tailwind CSS, or Shadcn UI. This skill provides patterns, conventions, and best practices for modern React development including component architecture, state management with Zustand, and responsive design.

Use when implementing automated testing with Playwright, including E2E tests, visual testing, or using the Playwright MCP tools for browser automation. This skill covers test patterns, selector strategies, and CI integration.

3 hooks across 2 events