qa-engineer
QA Engineer Skill
Analyze recent code changes in anytype-ts, map them to testable user-facing behavior, and generate Playwright E2E tests in the ../anytype-desktop-suite repository.
When to Use
Activate this skill when:
- After implementing a new feature or modifying existing functionality
- After editor/component changes that affect user interactions
- The user explicitly asks to add tests for recent changes
- After completing a task referenced in CLAUDE.md's "QA Engineer" section
Principles
- Change-driven — Only test what actually changed, don't generate tests for untouched code
- User-facing — Focus on observable behavior, not implementation details
- Compatible — Follow the existing test patterns in anytype-desktop-suite exactly
- Minimal — One test file per feature area, don't over-test
- Translation-aware — Always use translation keys, never hardcoded UI text
More from anyproto/anytype-ts
typescript-code-review
Perform comprehensive code reviews for TypeScript projects, analyzing type safety, best practices, performance, security, and code quality with actionable feedback
53update-docs
Update README documentation in the folder of changed components/abstractions to reflect code changes — keeps docs lean, precise, and in sync
36release-notes
Write and update release notes in whatsNew.ts with context-aware content generation
34dark-mode-check
Audit SCSS and TSX files for dark mode issues — missing variable usage, hardcoded colors, icon gaps, selector misuse, and inline dark overrides outside the theme folder
30commit-push
Commit staged/unstaged changes and push to the remote branch in one step
28