Write, fix, and review Cypress acceptance tests for Shopsys storefront. Use when working with Cypress test files (.cy.ts), adding test IDs (TIDs), or debugging test failures. Enforces project conventions: TID-based selectors, proper snapshot setup, and support file patterns.
Audits current storefront worktree or branch changes for code and artifacts that are unnecessary, dead, speculative, equivalent, redundant, or unrelated. Use before committing storefront changes, when simplifying a frontend diff, or when the user asks whether anything can be removed from a storefront implementation.
Audits current storefront worktree or branch changes for code and artifacts that are unnecessary, dead, speculative, equivalent, redundant, or unrelated. Use before committing storefront changes, when simplifying a frontend diff, or when the user asks whether anything can be removed from a storefront implementation.
Ad-hoc Pull Request Publisher โ commits the current changes, pushes the branch, opens a GitHub pull request against the repository's default branch, and creates a matching SSP Jira issue in the current sprint following the ad-hoc work convention (summary = PR title + " #<PR number>", PR link in the "Merge Request" field, no description, moved to In Progress). Works for any ad-hoc change โ fixes, small improvements, tooling, docs. Use when the user asks to publish/ship the current work end-to-end, or invokes /adhoc-pr.
Generates a PR description focused on business value using the project's PR template. Analyzes branch changes and writes a clear, user-facing explanation of what changed and why. Use when the user asks to create/write/generate a PR description, or invokes /pr-description.
Analyzes codebase implementation details. Call the codebase-analyzer agent when you need to find detailed information about specific components. As always, the more detailed your request prompt, the better! :)
Locates files, directories, and components relevant to a feature or task. Call `codebase-locator` with human language prompt describing what you're looking for. Basically a "Super Grep/Glob/LS tool" โ Use it if you find yourself desiring to use one of these tools more than once.
codebase-pattern-finder is a useful subagent for finding similar implementations, usage examples, or existing patterns that can be modeled after. It will give you concrete code examples based on what you're looking for! It's sorta like codebase-locator, but it will not only tell you the location of files, it will also give you code details!