Agent skill

Bug Fix

Lightweight entry point for fixing bugs with full traceability.

MITAuto-check passedTesting & QA

Install Bug Fix

skills CLI

$ npx skills add EmeaAppGbb/spec2cloud --skill bug-fix -a claude-code

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

GitHub CLI

$ gh skill install EmeaAppGbb/spec2cloud bug-fix --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/EmeaAppGbb/spec2cloud.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/bug-fix .claude/skills/bug-fix && 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 "bug-fix" agent skill from https://github.com/EmeaAppGbb/spec2cloud/tree/vNext/.github/skills/bug-fix into .claude/skills/bug-fix/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bug-fix", 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/EmeaAppGbb/spec2cloud/tree/vNext/.github/skills/bug-fix

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 EmeaAppGbb/spec2cloud --skill bug-fix -a codex

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

GitHub CLI

$ gh skill install EmeaAppGbb/spec2cloud bug-fix --agent codex

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

Manual copy

$ git clone --depth 1 https://github.com/EmeaAppGbb/spec2cloud.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/bug-fix .agents/skills/bug-fix && 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 "bug-fix" agent skill from https://github.com/EmeaAppGbb/spec2cloud/tree/vNext/.github/skills/bug-fix into .agents/skills/bug-fix/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bug-fix", 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 EmeaAppGbb/spec2cloud --skill bug-fix -a cursor

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

GitHub CLI

$ gh skill install EmeaAppGbb/spec2cloud bug-fix --agent cursor

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

Manual copy

$ git clone --depth 1 https://github.com/EmeaAppGbb/spec2cloud.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/bug-fix .cursor/skills/bug-fix && 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 "bug-fix" agent skill from https://github.com/EmeaAppGbb/spec2cloud/tree/vNext/.github/skills/bug-fix into .cursor/skills/bug-fix/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bug-fix", 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/EmeaAppGbb/spec2cloud.git --path .github/skills/bug-fix

--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 EmeaAppGbb/spec2cloud --skill bug-fix -a gemini-cli

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

GitHub CLI

$ gh skill install EmeaAppGbb/spec2cloud bug-fix --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/EmeaAppGbb/spec2cloud.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/bug-fix .gemini/skills/bug-fix && 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 "bug-fix" agent skill from https://github.com/EmeaAppGbb/spec2cloud/tree/vNext/.github/skills/bug-fix into .gemini/skills/bug-fix/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bug-fix", 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 EmeaAppGbb/spec2cloud bug-fix

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 EmeaAppGbb/spec2cloud --skill bug-fix -a github-copilot

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

Manual copy

$ git clone --depth 1 https://github.com/EmeaAppGbb/spec2cloud.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/bug-fix .github/skills/bug-fix && 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 "bug-fix" agent skill from https://github.com/EmeaAppGbb/spec2cloud/tree/vNext/.github/skills/bug-fix into .github/skills/bug-fix/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bug-fix", 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 EmeaAppGbb/spec2cloud --skill bug-fix -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 EmeaAppGbb/spec2cloud bug-fix --agent opencode

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

Manual copy

$ git clone --depth 1 https://github.com/EmeaAppGbb/spec2cloud.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/bug-fix .opencode/skills/bug-fix && 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 "bug-fix" agent skill from https://github.com/EmeaAppGbb/spec2cloud/tree/vNext/.github/skills/bug-fix into .opencode/skills/bug-fix/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bug-fix", 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: bug-fix
GitHub stars: 100
Token cost: ~2k tokens
SKILL.md length: 858 words
Files: 1
Skills in repo: 39
Repo updated: Apr 16, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Lightweight entry point for fixing bugs with full traceability.

Works in 8 steps: Identify the Relevant FRD → Create a Failing Test → Human Approval of the Test → …
Fixing bugs with test-first methodology and spec2cloud pipeline traceability
SKILL.md covers Role, Input, Process and Traceability Chain, plus 4 more sections
Calls npm, npx and git

What it does

Bug Fix is an agent skill from EmeaAppGbb/spec2cloud. Lightweight entry point for fixing bugs with full traceability. Takes a bug report, links to the relevant FRD, generates a failing test, fixes the code, and ships. Tracked as a micro-increment. Use when fixing bugs with test-first methodology and spec2cloud pipeline traceability.

Its SKILL.md is about 2k 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 Debugging, Failing and flaky tests and QA and bug reports. The licence is MIT.

When your agent uses it

Fixing bugs with test-first methodology and spec2cloud pipeline traceability
Tasks that involve Debugging
Tasks that involve Failing and flaky tests

Example prompts

“/bug-fix”

Requirements

Node.js

Workflow steps

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

Identify the Relevant FRD
Create a Failing Test
Human Approval of the Test
Verify the Test Fails
Fix the Code
Run Full Regression
Update State
Commit

What it can do on your machine

Read from SKILL.md and the folder at commit 8e76618. 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:
- npm
- npx
- git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npm, npx and git, 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

Bug Fix loads about 2k tokens when it runs. Until then it costs about 72 tokens; SKILL.md has 858 words of instructions outside code blocks.

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

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 passed

The automated check found no risky patterns in SKILL.md.

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 EmeaAppGbb/spec2cloud at commit 8e76618, republished under its MIT licence (© EmeaAppGbb). 858 words, ~1,955 tokens.

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

name: bug-fix
description: Lightweight entry point for fixing bugs with full traceability. Takes a bug report, links to the relevant FRD, generates a failing test, fixes the code, and ships. Tracked as a micro-increment. Use when fixing bugs with test-first methodology and spec2cloud pipeline traceability.

Bug Fix

Role

You are the Bug Fix Agent. You fast-track bug fixes through the spec2cloud pipeline with full traceability. Every bug fix starts with a failing test, links back to the FRD that defines the broken behavior, and ships as a micro-increment. You do NOT skip steps — test-first is mandatory.

Unlike planners, you execute the full fix cycle: identify → test → fix → verify → commit.

Input

A bug report containing:

Description — what is broken.
Steps to reproduce — exact sequence to trigger the bug.
Expected behavior — what should happen (per the FRD).
Actual behavior — what actually happens.
Environment (optional) — browser, OS, API version, etc.

If the bug report is incomplete, flag the missing information. Do NOT guess reproduction steps.

Process

Step 1 — Identify the Relevant FRD

Every bug is a deviation from specified behavior. Find the FRD that defines the expected behavior:

Search specs/frd-*.md for the feature area the bug affects.
Find the specific acceptance criterion or behavior description that the bug violates.
Document the linkage: "This bug violates acceptance criterion 3 of frd-user-auth.md".

If no FRD covers the broken behavior:

The behavior was never specified → this is a feature gap, not a bug. Flag it for the Extension Planner.
The FRD exists but the criterion is ambiguous → flag for spec refinement.

Step 2 — Create a Failing Test

Write a test that reproduces the bug:

Unit test — if the bug is in a single function or module.
Integration test — if the bug involves multiple components interacting.
E2e test — if the bug is a user-visible flow issue.

The test must:

Follow the existing test conventions (framework, file location, naming).
Describe the expected behavior in the test name: test("should reject duplicate email during registration", ...)
Assert the EXPECTED behavior (not the buggy behavior).
Reference the FRD: // Validates: frd-user-auth.md, AC-3

Step 3 — Human Approval of the Test

MANDATORY GATE. Present the test to the user for review before proceeding:

Show the test code and explain what it verifies.
Explain which FRD acceptance criterion it maps to.
Ask the user to approve or reject the test.

User Response	Action
Approve	Proceed to Step 4 (verify the test fails).
Reject with feedback	Revise the test based on feedback. Re-present.
Defer	Log the bug as a known issue in state.json. Resume previous work.

Do NOT proceed to fix the code until the user approves the test. The test defines what "fixed" means — the user must agree on that definition.

Step 4 — Verify the Test Fails

Run the test and confirm it fails with the expected error:

bash

# Unit test
npm test -- --grep "should reject duplicate email"

# E2e test
npx playwright test --grep "duplicate email"

If the test passes → the bug is not reproduced. Re-examine the reproduction steps and the test. Do NOT proceed until the test fails.

Step 5 — Fix the Code

Apply the minimal change to make the failing test pass:

Change as few files as possible.
Change as few lines as possible.
Do NOT refactor surrounding code.
Do NOT add features.
Do NOT fix other bugs you notice (file them separately).

The fix should be obvious from the diff. If the fix is complex, it may warrant a full increment rather than a bug-fix micro-increment.

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

Step 6 — Run Full Regression

After the fix, run the complete test suite:

bash

# All unit tests
npm test

# All e2e tests
npx playwright test

# Build verification
npm run build

Every test must pass — the bug-fix test AND all pre-existing tests. If any pre-existing test breaks, the fix is too broad or has side effects. Revise.

Step 7 — Update State

Update .spec2cloud/state.json with the micro-increment:

json

{
  "increments": {
    "bugfix-{nnn}": {
      "type": "bugfix",
      "frd": "frd-{feature}.md",
      "description": "Brief description of the fix",
      "status": "done",
      "testFile": "path/to/new-test.spec.ts",
      "fixedFiles": ["path/to/fixed-file.ts"],
      "completedAt": "ISO-timestamp"
    }
  }
}

Step 8 — Commit

Commit with the standard bug-fix format:

bash

git add -A
git commit -m "[bugfix] frd-user-auth: reject duplicate email during registration

- Added failing test: src/tests/auth/duplicate-email.test.ts
- Fixed: src/services/auth/register.ts (added unique constraint check)
- Validates: frd-user-auth.md, AC-3

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>"

Commit message format:

Subject: [bugfix] {frd-id}: {brief description}
Body: list the test file, fixed files, and FRD reference.

Traceability Chain

Every bug fix creates a complete traceability chain:

Bug Report
  → FRD (frd-{feature}.md, acceptance criterion N)
    → Failing Test (proves the bug exists)
      → Human Approval (user agrees the test captures the problem)
        → Fix (minimal code change)
          → Passing Test (proves the bug is fixed)
            → Commit (links all artifacts)
              → State (tracked as micro-increment)

This chain ensures:

The bug is linked to a specification (not ad hoc).
A regression test prevents the bug from recurring.
The fix is auditable and reversible.

Audit Log

Append to .spec2cloud/audit.log:

[ISO-timestamp] step=bugfix action=test-created bug=bugfix-{nnn} frd={frd-id} test={test-file} result=failing
[ISO-timestamp] step=bugfix action=test-approved bug=bugfix-{nnn} approver=human result=approved
[ISO-timestamp] step=bugfix action=fix-applied bug=bugfix-{nnn} files={fixed-files} result=done
[ISO-timestamp] step=bugfix action=regression-passed bug=bugfix-{nnn} result=all-green
[ISO-timestamp] step=bugfix action=committed bug=bugfix-{nnn} commit={sha} result=done

Decision Tree

Can identify relevant FRD? → Yes: create failing test. No: flag for Extension Planner.
Test reproduces the bug? → Yes: fix the code. No: re-examine reproduction steps.
Fix is minimal (< 50 lines)? → Yes: micro-increment. No: escalate to full increment.
All tests pass after fix? → Yes: update state and commit. No: revise fix.

Constraints

Test-first is mandatory. No fix without a failing test. No exceptions.
FRD linkage is mandatory. If no spec exists, it's a feature request.
Minimal change only. Refactoring goes in separate increments.
No silent fixes. Every fix is committed, logged, and tracked in state.
Regression must pass. If the fix breaks other tests, the fix is wrong.

Mandatory Completion Checklist

The orchestrator MUST verify ALL of the following before marking bug-fix as complete:

Bug is linked to a specific FRD (or flagged as a feature request if no FRD exists)
A failing test exists that reproduces the bug
Human approved the reproduction test (mandatory gate)
The fix is minimal (< 50 lines; larger fixes escalated to full increments)
The reproduction test now passes
Full regression suite passes (no other tests broken)
State JSON records the micro-increment; audit log has the fix entry
Commit uses [bugfix] {frd-id}: {description} format

BLOCKING: If any item is unchecked, the skill has NOT completed successfully. The orchestrator must loop back and complete the missing items.

Files

Just SKILL.md in .github/skills/bug-fix of EmeaAppGbb/spec2cloud.

Open the folder on GitHubat commit 8e76618

Compare with similar skills

Bug Fix 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.

Bug Fix compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Bug Fix this skillEmeaAppGbb/spec2cloud	100	—	~2k	Automated safety check: Pass	MIT	5 mo ago
Opsmill Dev Test Driving Bugsopsmill/infrahub	529	—	~4k	Automated safety check: Pass	Apache-2.0	today
Systematic Debuggingforyourhealth111-pixel/Vibe-Skills	3.6k	—	~2.6k	Automated safety check: Pass	Apache-2.0	1 mo ago
Bug To Patch GeneratorArabelaTso/Skills-4-SE	253	—	~4.4k	Automated safety check: Pass	Apache-2.0	1 mo ago
Fix The Classjoetawil7/first-pass	112	—	~1.5k	Automated safety check: Pass	MIT	6 days ago
Fix BugMelbourneDeveloper/dart_node	113	1 repos	~709	Automated safety check: Notes	None	23 days ago

Similar skills

Opsmill Dev Test Driving Bugs
opsmill/infrahub
Writes a single failing test that reproduces a bug after its root-cause analysis is complete, before any fix is written.
529 GitHub stars~4k tokensUpdated today
Testing & QAAuto-check passed
Systematic Debugging
foryourhealth111-pixel/Vibe-Skills
Root-cause route for actual bugs, failing tests, build errors, crashes, stack traces, and unexpected behavior.
3.6k GitHub stars~2.6k tokensUpdated 1 mo ago
Testing & QAAuto-check passed
Bug To Patch Generator
ArabelaTso/Skills-4-SE
Generate code fixes and patches from bug reports, failing test cases, error messages, and stack traces.
253 GitHub stars~4.4k tokensUpdated 1 mo ago
Testing & QAAuto-check passed
Fix The Class
joetawil7/first-pass
Bug-fix routine that fixes the whole class of bug, not just the reported instance.
112 GitHub stars~1.5k tokensUpdated 6 days ago
DevelopmentAuto-check passed
Fix Bug
MelbourneDeveloper/dart_node
Fix a bug using test-driven development. An agent skill from MelbourneDeveloper/dart_node.
113 GitHub starsUsed in 1 repo~709 tokens
Testing & QAAuto-check: notes
Red Green Fix
Comfy-Org/ComfyUI_frontend
Bug fix workflow that proves test validity with a red-then-green CI sequence.
2.1k GitHub stars~1.9k tokensUpdated today
Testing & QAAuto-check passed

Questions about Bug Fix

What does Bug Fix do?

Lightweight entry point for fixing bugs with full traceability. Bug Fix is an agent skill from EmeaAppGbb/spec2cloud. Lightweight entry point for fixing bugs with full traceability.

When should I use Bug Fix?

Bug Fix fits situations like: fixing bugs with test-first methodology and spec2cloud pipeline traceability; tasks that involve Debugging; tasks that involve Failing and flaky tests.

How do I install Bug Fix in Claude Code?

Run `npx skills add EmeaAppGbb/spec2cloud --skill bug-fix -a claude-code`. Or copy the skill folder (.github/skills/bug-fix in EmeaAppGbb/spec2cloud) into .claude/skills/bug-fix in your project. Claude Code loads it when a task matches its description.

How do I install Bug Fix in Codex?

Run `npx skills add EmeaAppGbb/spec2cloud --skill bug-fix -a codex`. Or copy the skill folder (.github/skills/bug-fix in EmeaAppGbb/spec2cloud) into .agents/skills/bug-fix in your project. Codex loads it when a task matches its description.

Can I use Bug Fix 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 EmeaAppGbb/spec2cloud --skill bug-fix -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/bug-fix, .gemini/skills/bug-fix, .github/skills/bug-fix and .opencode/skills/bug-fix in your project.

What does Bug Fix need to run?

Going by SKILL.md and its folder, Bug Fix needs the command-line tools its instructions call (npm, npx and git). Our summary lists: Node.js.

Does Bug Fix access the network?

SKILL.md contains no URLs. Its commands use npm, npx and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Bug Fix safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Bug Fix use?

Bug Fix is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Bug Fix use?

About 2k tokens (SKILL.md is roughly 7.8k 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 Bug Fix?

Skills that share tags, products or a category with Bug Fix: Opsmill Dev Test Driving Bugs (opsmill/infrahub, 529 stars), Systematic Debugging (foryourhealth111-pixel/Vibe-Skills, 3.6k stars), Bug To Patch Generator (ArabelaTso/Skills-4-SE, 253 stars) and Fix The Class (joetawil7/first-pass, 112 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Bug Fix?

EmeaAppGbb (a GitHub organization) maintains it in EmeaAppGbb/spec2cloud, which has 100 GitHub stars. The repository holds 39 skills in this directory. The repository was last updated on April 16, 2026.

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

Install Bug Fix

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

Bug Fix

Role

Input

Process

Step 1 — Identify the Relevant FRD

Step 2 — Create a Failing Test

Step 3 — Human Approval of the Test

Step 4 — Verify the Test Fails

Step 5 — Fix the Code

Step 6 — Run Full Regression

Step 7 — Update State

Step 8 — Commit

Traceability Chain

Audit Log

Decision Tree

Constraints

Mandatory Completion Checklist

Files

Compare with similar skills

Similar skills

More from EmeaAppGbb/spec2cloud

Related

Questions about Bug Fix