dev

Use this agent when you need to manually test application functionality in a browser. This includes: after implementing new features or UI components, after making changes to navigation or routing logic, when layout or styling updates have been made, when the user requests verification of application behavior, or when validating that recent code changes work as expected in the browser. Examples: <example> Context: The user has just implemented a new login form component. user: "I've finished implementing the login form. Can you verify it works correctly?" assistant: "I'll use the Task tool to launch the browser-test-runner agent to test the login form functionality and verify it works as expected." </example> <example> Context: After updating navigation menu styling. user: "I've updated the navigation menu styles" assistant: "Let me use the browser-test-runner agent to verify the navigation menu displays correctly and all links work properly." </example> <example> Context: User has made several changes to the application. user: "I've added the dashboard page and updated the routing" assistant: "Since you've made significant changes to routing and added a new page, I'll launch the browser-test-runner agent to test navigation and verify the dashboard displays correctly." </example>

Use this agent when the user requests implementation of features, bug fixes, refactoring, or any code changes to the application. This agent should be your primary choice for executing development work that requires careful planning and understanding of the project structure. Examples: - user: 'Add a new authentication module to handle OAuth2' assistant: 'I'll use the lead-developer agent to implement the OAuth2 authentication module' <commentary>Since the user is requesting a significant feature implementation, use the lead-developer agent who will review the README and plan the work carefully.</commentary> - user: 'Fix the bug in the user registration flow' assistant: 'Let me use the lead-developer agent to investigate and fix the registration bug' <commentary>Bug fixes require careful analysis and planning, making this appropriate for the lead-developer agent.</commentary> - user: 'Refactor the database layer to use repository pattern' assistant: 'I'll launch the lead-developer agent to refactor the database layer' <commentary>Architectural changes need thorough planning and understanding of the codebase, which the lead-developer agent provides.</commentary>

Commit and push changes

Creates a GitHub PR for current work. Handles branch creation, committing, pushing, and PR creation.

Creates a new git worktree for parallel development. Use when the user wants to work on something in a separate worktree, start parallel work, or isolate changes.

Restructures a git project's directories so all worktrees (including main) are siblings under a common parent. Use when setting up a project for the sibling-worktree layout.