sync-testing-skill

Extract new test patterns from package test suites and update testing.mdc.

16.5k|995|Updated Dec 2, 2019
One-click install
npx skills add https://github.com/udecode/plate --skill sync-testing-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync-testing-skill
Source: https://github.com/udecode/plate/tree/main/.agents/skills/sync-testing-skill
Command: npx skills add https://github.com/udecode/plate --skill sync-testing-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the discovery of new test patterns from package tests and updates the central testing.mdc to reflect them.

Core Features & Use Cases

  • Scan package tests to identify patterns not present in testing.mdc.
  • Update @.agents/rules/testing.mdc with the newly discovered patterns, keeping guidelines DRY and concise.
  • Use case: as codebases grow, automatically refresh the testing standards to cover new test styles.

Quick Start

Scan package tests and update @.agents/rules/testing.mdc with new patterns.

Frequently Asked Questions about sync-testing-skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically extract new test patterns from package test suites?

To automatically extract new test patterns from package test suites, scan the repository and identify test styles not present in the central testing.mdc, then refresh the documentation to reflect them.

What is the best way to keep testing guidelines synced with emerging test styles?

Keeping testing guidelines synced with emerging test styles requires scanning package tests to identify new patterns and updating the central testing.mdc file to ensure consistent guidance across the codebase.

Do I need external tools to sync testing rules across multiple packages?

No external tools are needed to sync testing rules across packages beyond standard repository access, as the process adheres to existing tooling for pattern extraction and documentation updates.

When should I update central testing documentation with newly discovered patterns?

You should update central testing documentation with newly discovered patterns when codebases grow and new test styles emerge, ensuring the guidelines remain DRY, concise, and consistent across relevant packages.

Can I apply testing pattern synchronization across different packages in a monorepo?

Yes, you can apply testing pattern synchronization across relevant packages in a repository, identifying patterns not present in testing.mdc and refreshing the central file to ensure consistent testing guidance.

Why does my central testing.mdc file not reflect the latest test patterns?

Your central testing.mdc file does not reflect the latest test patterns because it has not been refreshed, requiring a scan of package test suites to extract new styles and update the guidelines.