TypingMindTypingMindThe best frontend for AI
Cxc Dev Testing logo

Cxc Dev Testing

Community
lidge-jun
cxc-dev-testing

Use for tests and release verification. Triggers: regression test, Playwright, E2E, contract test, coverage, CI flake, TDD, 테스트, 회귀 테스트, 품질 게이트.

Overview

Publisherlidge-jun
Repositorycodexclaw
Skill namecxc-dev-testing
Stars
51
Forks
10
Bundled files
22
LicenseMIT
Links
Skill sourceRepositoryHomepage
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 22 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by lidge-jun on GitHub. Read the source before you install it.

Installation

Install the Cxc Dev Testing AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/lidge-jun/codexclaw/tree/main/plugins/codexclaw/skills/dev-testing
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/lidge-jun/codexclaw.git /tmp/codexclaw
mkdir -p .claude/skills
cp -r /tmp/codexclaw/plugins/codexclaw/skills/dev-testing .claude/skills/cxc-dev-testing
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Cxc Dev Testing in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Cxc Dev Testing on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Cxc Dev Testing is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Testing & QA

Balance: ~40% Backend/API, ~40% Frontend/E2E (Playwright), ~20% Cross-cutting (CI, Security, TDD, Coverage) -- directional guidance, not a hard ratio. Scope: test harnesses, fixtures, mock policy, runners, Playwright, CI gates, coverage. Root-cause analysis and debugging playbooks → dev-debugging.

  • This skill owns test adequacy; dev-code-reviewer owns finding severity and review process.
  • CI pipeline ownership and deployment verification: see dev-devops.
  • Data pipeline testing and ETL validation: see dev-data.
  • Design direction context for rendered verification: see dev-uiux-design. This skill activates by change-surface when work needs verification depth, regression coverage, or a reproducible test harness.

Class, fast path, rule authority, proof, and safety: dev. Current/public evidence: dev routing.

1.3 Risk-First Priorities

  1. auth / session / permission boundaries
  2. money movement, quota, credits
  3. data mutation and irreversible actions
  4. file upload / parsing / external webhooks
  5. shared API contracts used by frontend clients
  6. error paths, retries, rollback behavior

1.4 Harness Selector

ProblemPrimary HarnessAvoid
pure business ruleunit / service testbrowser test
route + middleware + serializationAPI integration testmocking the route itself
DB query / migration / transactionreal DB integration testfake repository for SQL correctness
frontend consuming backend JSONcontract testmanual-only verification
rendered critical flowPlaywright smokeasserting internal React state

Test-oracle rules apply before accepting green: oracle integrity.

Modular References

ConditionReference
Choose verification depth or test a CRUD slicecore/crud-test-matrix.md
Choose model, distribution, fixture policy, or general test rulestest-strategy.md
New feature unit/service/integration tests (not regression/contract)edge-first-testing.md
Property/invariant-heavy or mutation testingproperty-and-mutation-testing.md
Backend/API, database, or contract verificationapi-test-patterns.md; backend-testing.md
Rendered browser tests or exploratory browser QAbrowser-testing.md
CI test stages, failures, or flakesci-integration.md; ci-pipeline.md
ENFORCE_TDD, AI regressions, or test-induced production guardstdd-and-regressions.md
Accessibility, trace/log verification, security, coverage, or pre-flightacceptance-gates.md
Write acceptance criteriaacceptance-row-reachability.md
Test expectations, prose seams, override/default/fallback fixturestest-oracle-integrity.md
Implementation completion with test/config changespatch-integrity.md
Scarce, paid, rate-limited, or opaque evaluatorslimited-oracle-evaluation.md
Performance/load or C3+ production readinessload-testing.md
ML/LLM evaluation or quality gatesml-evaluation.md
Desktop suites and CI matrixNative desktop acceptance

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Cxc Dev Testing AI skill do?

Use for tests and release verification. Triggers: regression test, Playwright, E2E, contract test, coverage, CI flake, TDD, 테스트, 회귀 테스트, 품질 게이트.

Why use Cxc Dev Testing on TypingMind?

Because you install it once and use it with any model. Cxc Dev Testing is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Cxc Dev Testing in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/lidge-jun/codexclaw/tree/main/plugins/codexclaw/skills/dev-testing. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Cxc Dev Testing?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Cxc Dev Testing?

As many as you like. As long as a model supports skills, you can use Cxc Dev Testing with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Cxc Dev Testing AI skill free?

Yes. It is published on GitHub by lidge-jun under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

Related AI Skills

View all
openclaw logo

Telegram E2e Userbot

openclaw
OrganizationPopular

Prove user-visible OpenClaw Telegram behavior on Telegram's Test Server with Convex-leased team credentials; drive real-user turns and record messages, edits, deletions, reactions, typing, or rich…

82.2K
391K
45 files
View
affaan-m logo

Module Regression

affaan-m
CommunityPopular

Govern cross-module regression in large repositories with a REGRESSION.md ledger that records each module's downstream consumers and executable acceptance command. After a change, run the changed…

41.4K
277.3K
2 files
View
affaan-m logo

Test Collaboration

affaan-m
CommunityPopular

Inventory and govern a project's test assets. Connect requirements, business rules, risks, bugs, and cross-boundary contracts to stable TEST-IDs and executable evidence in the repository's existing…

41.4K
277.3K
2 files
View
affaan-m logo

Competitive Report Structure

affaan-m
CommunityPopular

Use after benchmark-methodology has produced scored competitor profile cards. Assembles findings into a decision-grade report: landscape map, competitor profiles, benchmarking matrix, white-space…

40.4K
270.2K
1 files
View

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇