Testing And Ci

OrganizationPopular

iflytek

testing-and-ci

Testing conventions, CI pipeline rules, and smoke test coverage for SkillHub. Ensures agents write tests correctly and understand the CI gate requirements.

Overview

Publisher	iflytek
Repository	`skillhub`
Skill name	`testing-and-ci`
Stars	5.2K
Forks	841
Bundled files	Instructions only
License	Apache-2.0
Links	Skill source Repository Homepage

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.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by iflytek on GitHub. Read the source before you install it.

Installation

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

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.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/iflytek/skillhub/tree/main/.agents/skills/testing-and-ci
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.

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/iflytek/skillhub.git /tmp/skillhub
mkdir -p .claude/skills
cp -r /tmp/skillhub/.agents/skills/testing-and-ci .claude/skills/testing-and-ci

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Testing And Ci 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 Testing And Ci 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 Testing And Ci 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 and CI Skill

Trigger

Use this skill when:

Adding or modifying backend tests
Adding or modifying frontend tests
Changing CI/CD workflows
Adding smoke tests or E2E tests

Rules

Backend Testing

Tests live alongside source in each module's src/test/java/:

server/skillhub-app/src/test/java/ — Controller integration tests, service tests
server/skillhub-domain/src/test/java/ — Domain service unit tests
server/skillhub-auth/src/test/java/ — Auth flow tests

Tools: JUnit 5 + Mockito + AssertJ + Spring Boot test slices (@WebMvcTest, @DataJpaTest)

Build commands:

bash
make test-backend-app   # skillhub-app + dependencies (includes -am)
make test-backend       # all backend modules

Never run ./mvnw -pl skillhub-app clean test directly under server/. skillhub-app depends on sibling modules, and a standalone clean build can fall back to stale artifacts from the local Maven repository, surfacing misleading cannot find symbol and signature-mismatch errors. Use -am, or the Makefile targets above.

Test naming conventions:

Controller tests: {ControllerName}Test.java (e.g., SkillControllerTest.java)
Service tests: {ServiceName}Test.java
Integration tests: {FlowName}IntegrationTest.java
Security tests: {ControllerName}SecurityTest.java

Frontend Testing

Tools: Vitest (unit), Playwright (E2E)

bash
make test-frontend            # Vitest unit tests (pnpm run test)
make test-e2e-frontend        # Playwright E2E tests
make test-e2e-smoke-frontend  # Playwright smoke tests (subset)

E2E tests live in web/e2e/.

Smoke Tests

Smoke tests validate end-to-end operator workflows against a running backend:

Script	Purpose
`scripts/smoke-test.sh`	Basic API health, auth, label CRUD
`scripts/namespace-smoke-test.sh`	Namespace creation, membership, publishing
`scripts/governance-smoke-test.sh`	Governance and moderation flows
`scripts/promotion-smoke-test.sh`	Skill promotion between scopes

When operator-facing workflows change, update the corresponding smoke test.

CI Pipeline

GitHub Actions workflows in .github/workflows/:

Workflow	Trigger	Purpose
`pr-tests.yml`	PR	Backend + frontend unit tests
`pr-e2e.yml`	PR	E2E smoke tests against staging
`pr-batch-test-deploy.yml`	workflow_dispatch	Batch test and deploy
`publish-images.yml`	release published / workflow_dispatch	Build and publish Docker images to GHCR
`deploy-docs.yml`	push to docs	Deploy documentation site
`issue-triage.yml`	issues	Auto-triage incoming issues
`issue-backlog-rescore.yml`	cron (every 6h)	Rescore backlog issues
`release-notes.yml`	workflow_dispatch	Generate release notes
`deepwiki.yml`	release published	Update DeepWiki documentation
`claim-issue-reward.yml`	issue_comment	Auto-claim issue rewards
`statistic-member-reward.yml`	cron/schedule	Calculate member rewards

All workflows live in .github/workflows/. Deno scripts for triage, release notes, and rewards live in .github/scripts/.

Staging

Before opening a PR, validate with staging:

bash
make staging          # Build backend Docker image + frontend static + smoke test
make staging-down     # Tear down
SERVICE=web make staging-logs  # View Nginx logs

Staging validates the containerized deployment path:

Backend: built as Docker image from local source (Dockerfile.dev)
Frontend: built as static files (pnpm build), served by Nginx
Dependencies: same Postgres/Redis/MinIO as local dev

If staging passes, the environment stays running at:

Web UI: http://localhost
Backend API: http://localhost:8080

Pre-PR Testing Checklist

make test-backend-app passes
make typecheck-web passes
make lint-web passes (if frontend changed)
make staging passes (full regression)
If API changed: make generate-api run and generated file committed
New behavior has corresponding tests

Frequently asked questions

What does the Testing And Ci AI skill do?

Testing conventions, CI pipeline rules, and smoke test coverage for SkillHub. Ensures agents write tests correctly and understand the CI gate requirements.

Why use Testing And Ci on TypingMind?

Because you install it once and use it with any model. Testing And Ci 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 Testing And Ci in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/iflytek/skillhub/tree/main/.agents/skills/testing-and-ci. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Testing And Ci?

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 Testing And Ci?

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

Is the Testing And Ci AI skill free?

Yes. It is published on GitHub by iflytek under the Apache-2.0 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.

View all

Documentation Lookup

affaan-m

CommunityPopular

Use up-to-date library and framework docs via Context7 MCP instead of training data. Activates for setup questions, API references, code examples, or when the user names a framework (e.g. React,…

Mle Workflow

Production machine-learning engineering workflow for data contracts, reproducible training, model evaluation, deployment, monitoring, and rollback. Use when building, reviewing, or hardening ML…

Diagnosing Bugs

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.

E2e Testing

Patrones de pruebas E2E con Playwright, Page Object Model, configuración, integración CI/CD, gestión de artefactos y estrategias para pruebas inestables.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Testing and CI Skill

Trigger

Rules

Backend Testing

Frontend Testing

Smoke Tests

CI Pipeline

Staging

Pre-PR Testing Checklist

Frequently asked questions

Related AI Skills

Set up your own AI workspace now