Agent skill

Dev Workflow

The complete development workflow for SkillHub contributors including local dev, staging validation, testing, and PR creation.

Apache-2.0Auto-check: notesTesting & QA

Install Dev Workflow

skills CLI

$ npx skills add iflytek/skillhub --skill dev-workflow -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install iflytek/skillhub dev-workflow --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/iflytek/skillhub.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/dev-workflow .claude/skills/dev-workflow && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "dev-workflow" agent skill from https://github.com/iflytek/skillhub/tree/main/.agents/skills/dev-workflow into .claude/skills/dev-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dev-workflow", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/iflytek/skillhub/tree/main/.agents/skills/dev-workflow

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add iflytek/skillhub --skill dev-workflow -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install iflytek/skillhub dev-workflow --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/iflytek/skillhub.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/dev-workflow .agents/skills/dev-workflow && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "dev-workflow" agent skill from https://github.com/iflytek/skillhub/tree/main/.agents/skills/dev-workflow into .agents/skills/dev-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dev-workflow", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add iflytek/skillhub --skill dev-workflow -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install iflytek/skillhub dev-workflow --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/iflytek/skillhub.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/dev-workflow .cursor/skills/dev-workflow && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "dev-workflow" agent skill from https://github.com/iflytek/skillhub/tree/main/.agents/skills/dev-workflow into .cursor/skills/dev-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dev-workflow", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/iflytek/skillhub.git --path .agents/skills/dev-workflow

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add iflytek/skillhub --skill dev-workflow -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install iflytek/skillhub dev-workflow --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/iflytek/skillhub.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/dev-workflow .gemini/skills/dev-workflow && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "dev-workflow" agent skill from https://github.com/iflytek/skillhub/tree/main/.agents/skills/dev-workflow into .gemini/skills/dev-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dev-workflow", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install iflytek/skillhub dev-workflow

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add iflytek/skillhub --skill dev-workflow -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/iflytek/skillhub.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/dev-workflow .github/skills/dev-workflow && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "dev-workflow" agent skill from https://github.com/iflytek/skillhub/tree/main/.agents/skills/dev-workflow into .github/skills/dev-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dev-workflow", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add iflytek/skillhub --skill dev-workflow -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install iflytek/skillhub dev-workflow --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/iflytek/skillhub.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/dev-workflow .opencode/skills/dev-workflow && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "dev-workflow" agent skill from https://github.com/iflytek/skillhub/tree/main/.agents/skills/dev-workflow into .opencode/skills/dev-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dev-workflow", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: dev-workflow
GitHub stars: 5.2k
Token cost: ~1.7k tokens
SKILL.md length: 526 words
Files: 1
Skills in repo: 28
Repo updated: Oct 8, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

The complete development workflow for SkillHub contributors including local dev, staging validation, testing, and PR creation.

Works in 4 steps: Local Development (fast iteration) → Testing → Staging Regression (pre-PR validation) → …
Tasks that involve QA and bug reports
SKILL.md covers Trigger, Prerequisites and Workflow Stages
Calls make, java and tsc

What it does

Dev Workflow is an agent skill from iflytek/skillhub. The complete development workflow for SkillHub contributors including local dev, staging validation, testing, and PR creation. Ensures agents follow the correct sequence of steps.

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA, covering QA and bug reports. It works with Docker, Java and pnpm. The repository describes itself as: Self-hosted, open-source agent skill registry for enterprises. Publish & version skill packages, govern with RBAC and audit logs, deploy on-premise with Docker or Kubernetes. The licence is Apache-2.0.

When your agent uses it

Tasks that involve QA and bug reports

Example prompts

“/dev-workflow”

Requirements

Node.js
Docker

Workflow steps

4 steps, taken from the step headings in SKILL.md.

Local Development (fast iteration)
Testing
Staging Regression (pre-PR validation)
Pull Request

What it can do on your machine

Read from SKILL.md and the folder at commit 7352597. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- make
- java
- tsc
- pnpm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use pnpm, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Dev Workflow loads about 1.7k tokens when it runs. Until then it costs about 48 tokens; SKILL.md has 526 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~48
When it runs · the whole SKILL.md, loaded when a task matches: ~1.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

NoteMentions a .env fileSKILL.md:118

ase-config` | Validate release env vars (.env.release) |

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from iflytek/skillhub at commit 7352597, republished under its Apache-2.0 licence (© iflytek). 526 words, ~1,651 tokens.

Download SKILL.mdSave it as .claude/skills/dev-workflow/SKILL.md (or your agent's skills folder).

name: dev-workflow
description: The complete development workflow for SkillHub contributors including local dev, staging validation, testing, and PR creation. Ensures agents follow the correct sequence of steps.
license: Apache-2.0

Development Workflow Skill

Trigger

Use this skill when:

Starting local development
Running tests or validation
Preparing a pull request
Setting up the development environment
Working with parallel agent worktrees

Prerequisites

Java 21+ (java -version)
Maven wrapper (./mvnw in server/)
Node.js + pnpm
Docker + docker compose
gh CLI (for PR creation)
curl (for smoke tests and health checks)

Workflow Stages

Stage 1: Local Development (fast iteration)

One-command start:

bash

make dev-all          # Start full stack: Postgres, Redis, MinIO, scanner, backend, frontend
make dev-all-down     # Stop everything
make dev-all-reset    # Full reset (clears data volumes)
make dev-status       # Check service status

Access points:

Web UI: http://localhost:3000
Backend API: http://localhost:8080
Scanner: http://localhost:8000

Individual components:

bash

make dev              # Start dependency services only (Postgres, Redis, MinIO, scanner)
make dev-server       # Start backend in foreground (blocking)
make dev-web          # Start Vite dev server (HMR enabled)
make dev-server-restart # Restart backend process
make dev-down         # Stop dependency services
make dev-logs         # View backend logs (use SERVICE=frontend for frontend logs)

Backend development: After editing Java code, run make dev-server-restart.

Frontend development: Vite HMR enabled — save a file for instant browser updates.

Scanner: The security scanner is enabled by default in dev. Health checked at http://localhost:8000/health.

Stage 2: Testing

Command	Scope	Notes
`make test-backend-app`	Backend unit tests	skillhub-app + dependencies (`-am`)
`make test-backend`	All backend modules	All modules via `./mvnw test`
`make test-frontend`	Frontend unit tests	Vitest (pnpm run test)
`make test-e2e-frontend`	Frontend E2E tests	Playwright
`make test-e2e-smoke-frontend`	Frontend E2E smoke	Playwright subset
`make typecheck-web`	TypeScript type check	`tsc --noEmit`
`make lint-web`	ESLint check	Frontend linting

Important: Never run ./mvnw -pl skillhub-app clean test directly under server/. Use -am or Makefile targets to include dependent modules.

Stage 3: Staging Regression (pre-PR validation)

bash

make staging          # Build backend Docker image + frontend static + smoke test
make staging-down     # Tear down
make staging-logs     # View backend logs
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
Smoke test runs against staging via scripts/smoke-test.sh

Staging URLs:

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

Staging credentials (for bootstrap admin):

Username: admin
Password: Admin@staging2026

Stage 4: Pull Request

bash

make pr               # Push branch + create PR (requires gh CLI)

Requirements:

gh CLI installed and authenticated
Not on main/master branch
All changes committed (will prompt if uncommitted changes exist)

Useful Commands

Command	Description
`make generate-api`	Regenerate OpenAPI types from running backend
`make namespace-smoke`	Namespace workflow smoke test
`make db-reset`	Reset database only (Flyway migrate)
`make validate-release-config`	Validate release env vars (.env.release)
`./scripts/smoke-test.sh`	Basic API smoke test (health, auth, labels)
`./scripts/namespace-smoke-test.sh`	Namespace CRUD + membership smoke test
`./scripts/check-openapi-generated.sh`	Verify OpenAPI types are not stale
`make parallel-init TASK=name`	Create parallel worktree for agent

Show full SKILL.md (189 more words)Show less

Mock Auth Users

User ID	Role	Header
`local-user`	Regular user	`X-Mock-User-Id: local-user`
`local-admin`	Super admin	`X-Mock-User-Id: local-admin`

Bootstrap admin (local profile):

Username: admin
Password: ChangeMe!2026

Smoke Test Coverage

scripts/smoke-test.sh validates:

Health endpoint (/actuator/health → 200)
Prometheus metrics (/actuator/prometheus → 200)
Namespaces API (/api/v1/namespaces → 200)
Auth required (/api/v1/auth/me → 401 without session)
User registration flow (with CSRF)
Auth me with session
Password change
Logout + verify 401 after
Admin login
Label CRUD (admin only)

Additional smoke tests:

scripts/namespace-smoke-test.sh — Namespace creation, membership, publishing
scripts/governance-smoke-test.sh — Governance and moderation
scripts/promotion-smoke-test.sh — Skill promotion between scopes

Parallel Agent Workflow

For parallel agent development with isolated worktrees:

bash

make parallel-init TASK=feature-name           # Create worktree
make parallel-sync SOURCES="feat1 feat2"       # Merge feature branches
make parallel-up SOURCES="feat1 feat2"         # Merge + start dev environment
make parallel-down                             # Stop parallel environment

See docs/13-parallel-workflow.md for full details.

Commit Style

Use conventional commit format:

<type>(<scope>): <description>

Examples:

feat(auth): add local account login
fix(publish): resolve null pointer when skill metadata is missing name
docs(deploy): clarify runtime image usage
test(namespace): add membership service edge case tests
refactor(review): extract query repository for governance list
chore(ci): add parallel workflow scripts

Common Issues

Issue	Solution
Backend won't start	Check Java version (`java -version`), must be 21+
Port 8080 in use	`lsof -i :8080` to find and kill the process
Maven download timeout	Configure mirror in `~/.m2/settings.xml`
Frontend won't start	Run `make web-deps` to ensure node_modules exist
Staging build fails	Check `Dockerfile.dev` and ensure Maven build succeeds first
CSRF errors in tests	Ensure cookie jar is shared and CSRF token refreshed after login

Files

Just SKILL.md in .agents/skills/dev-workflow of iflytek/skillhub.

Open the folder on GitHubat commit 7352597

Compare with similar skills

Dev Workflow next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Dev Workflow compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Dev Workflow this skilliflytek/skillhub	5.2k	—	~1.7k	Automated safety check: Notes	Apache-2.0	today
DeerFlow Smoke Testbytedance/deer-flow	83k	—	~2.5k	Automated safety check: Notes	MIT	today
Codex Plugin QAcode-yeongyu/oh-my-openagent	70k	1 repos	~1.9k	Automated safety check: Pass	Custom licence	today
OpenWork Desktop CDP Driverdifferent-ai/openwork	24k	—	~465	Automated safety check: Pass	Custom licence	today
Weavebench Cua ReproduceAMAP-ML/LongHorizon-Harness	1.7k	—	~1.6k	Automated safety check: Pass	MIT	1 mo ago
OpenCode QA Toolkitcode-yeongyu/oh-my-openagent	70k	—	~2.9k	Automated safety check: Pass	Custom licence	today

Similar skills

DeerFlow Smoke Test
bytedance/deer-flow
Walks through an end-to-end smoke test of a DeerFlow deployment: pull the latest code, deploy with Docker or locally, verify services, run health checks and write a report.
83k GitHub stars~2.5k tokensUpdated today
Testing & QAAuto-check: notes
Codex Plugin QA
code-yeongyu/oh-my-openagent
Tests the omo Codex plugin in an isolated CODEX_HOME with a local mock model, proving hooks fired through app-server notifications without touching ~/.codex.
70k GitHub starsUsed in 1 repo~1.9k tokens
Testing & QAAuto-check passed
OpenWork Desktop CDP Driver
different-ai/openwork
Drives a running OpenWork desktop window over CDP from the shell to evaluate JS, take screenshots, start sessions and send prompts for hand checks.
24k GitHub stars~465 tokensUpdated today
Testing & QAAuto-check passed
Weavebench Cua Reproduce
AMAP-ML/LongHorizon-Harness
Reproduce CUA-Harness experiments on WeaveBench from a GitHub checkout.
1.7k GitHub stars~1.6k tokensUpdated 1 mo ago
Testing & QAAuto-check passed
OpenCode QA Toolkit
code-yeongyu/oh-my-openagent
Tests the opencode coding agent itself: its CLI, server, plugin hooks and events, the terminal UI under tmux, and its SQLite session database, using tested helper scripts.
70k GitHub stars~2.9k tokensUpdated today
Testing & QAAuto-check passed
Desktop Dual Repo Test
Eynzof/Hermes-CN-Desktop
A skill your agent uses when starting or verifying Hermes Agent CN Desktop with the latest Hermes-CN-Desktop and Hermes-CN-Core branches — dev smoke test (pnpm tauri:dev), packaged beta/release…
1.7k GitHub stars~1.8k tokensUpdated 17 days ago
Testing & QAAuto-check passed

Questions about Dev Workflow

What does Dev Workflow do?

The complete development workflow for SkillHub contributors including local dev, staging validation, testing, and PR creation. Dev Workflow is an agent skill from iflytek/skillhub. The complete development workflow for SkillHub contributors including local dev, staging validation, testing, and PR creation.

When should I use Dev Workflow?

Dev Workflow fits situations like: tasks that involve QA and bug reports.

How do I install Dev Workflow in Claude Code?

Run `npx skills add iflytek/skillhub --skill dev-workflow -a claude-code`. Or copy the skill folder (.agents/skills/dev-workflow in iflytek/skillhub) into .claude/skills/dev-workflow in your project. Claude Code loads it when a task matches its description.

How do I install Dev Workflow in Codex?

Run `npx skills add iflytek/skillhub --skill dev-workflow -a codex`. Or copy the skill folder (.agents/skills/dev-workflow in iflytek/skillhub) into .agents/skills/dev-workflow in your project. Codex loads it when a task matches its description.

Can I use Dev Workflow in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add iflytek/skillhub --skill dev-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/dev-workflow, .gemini/skills/dev-workflow, .github/skills/dev-workflow and .opencode/skills/dev-workflow in your project.

What does Dev Workflow need to run?

Going by SKILL.md and its folder, Dev Workflow needs the command-line tools its instructions call (make, java, tsc and pnpm). Our summary lists: Node.js; Docker.

Does Dev Workflow access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Dev Workflow safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Dev Workflow use?

Dev Workflow is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Dev Workflow use?

About 1.7k tokens (SKILL.md is roughly 6.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Dev Workflow?

Skills that share tags, products or a category with Dev Workflow: DeerFlow Smoke Test (bytedance/deer-flow, 83k stars), Codex Plugin QA (code-yeongyu/oh-my-openagent, 70k stars), OpenWork Desktop CDP Driver (different-ai/openwork, 24k stars) and Weavebench Cua Reproduce (AMAP-ML/LongHorizon-Harness, 1.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Dev Workflow?

iflytek (a GitHub organization) maintains it in iflytek/skillhub, which has 5,157 GitHub stars. The repository holds 28 skills in this directory. The repository was last updated on October 8, 2026.

Source: iflytek/skillhub on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Dev Workflow

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Development Workflow Skill

Trigger

Prerequisites

Workflow Stages

Stage 1: Local Development (fast iteration)

Stage 2: Testing

Stage 3: Staging Regression (pre-PR validation)

Stage 4: Pull Request

Useful Commands

Mock Auth Users

Smoke Test Coverage

Parallel Agent Workflow

Commit Style

Common Issues

Files

Compare with similar skills

Similar skills

More from iflytek/skillhub

Related

Questions about Dev Workflow