Add and standardize data-testid attributes across frontend source files.
npx skills add https://github.com/10knamesmore/dotfiles --skill testid-adder
Please help me install this Agent Skill. Skill: testid-adder Source: https://github.com/10knamesmore/dotfiles/tree/main/general/skills/testid-adder Command: npx skills add https://github.com/10knamesmore/dotfiles --skill testid-adder
This Skill ensures frontend testids are added and audited consistently across a codebase, enabling reliable automated tests without exposing sensitive information.
Run the testid-adder on your frontend project to audit and annotate testids, then review the proposed patch and commit.
High-intent search queries and answers about installing and using this skill.
To add data-testid attributes without altering the DOM, this Skill locates root components and recursively annotates necessary child components, applying a semantic naming convention while strictly avoiding structural HTML changes.
Standardizing data-testid selectors for Playwright involves enforcing a page/component/element/interactWay naming convention, checking for duplicates, and updating a centralized testid mapping document to ensure stable, semantic test selectors.
Auditing frontend testids to avoid duplicates requires scanning source files to check existing data-testid attributes, enforcing a standardized naming spec, and coordinating updates through a patch-and-review flow using diff tooling.
Yes, you can incrementally add testids to new interactive elements. The Skill scans components to attach essential data-testid attributes and produces a proposed patch for review without modifying the underlying DOM hierarchy.
No, adding data-testid attributes does not expose sensitive information. The Skill ensures frontend testids are added and audited consistently, enabling reliable automated tests while explicitly preventing the exposure of sensitive data.
You should avoid automated data-testid mapping when your frontend components lack a clear root structure for recursive coverage, or when your project lacks a defined testid spec to enforce the required page/component/element/interactWay naming convention.
JaylaelikeProvide Next.js App Router patterns for Server Components, streaming, and parallel routes.
CodySwannGTDefine Playwright selector best practices for Expo web apps using testID and aria-label.
marcustaAutomate Playwright end-to-end tests for user flows and forms.
whitebearditGuide frontend markup to use semantic HTML and data-testid attributes for stable Playwright testing.
