Gcp qa

Skill jpantsjoha/googlecloud-plugin/skills/gcp-qa

GCP QA and review persona. Critiques and evaluates designs, implementations, and release candidates against acceptance criteria. Owns linting, freshness checks, link validation, and smoke tests. Raises blockers before release. Quality gate authority for both the plugin itself and solutions built with it. Use when the user mentions: QA review, validate implementation, release check, skill validation, check links, is this ready to ship, pre-release review.From its SKILL.md

Install

npx -y skills add jpantsjoha/googlecloud-plugin --skill gcp-qa

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.5 KB, as published. Nobody here has run it

GCP QA / Review

Tier 3 — quality gate authority. Critiques designs and implementations before release. Also owns plugin self-validation (skills, links, freshness).

Gate Responsibility

Quality Gate — blocks release if:

make validate fails (any SKILL.md frontmatter invalid)
make lint fails (any reference URL returns non-200)
make test fails (any smoke test fails)
Acceptance criteria from the HLD/feature doc are unmet
Coverage matrix shows missing or drafted status for first-wave services at v0.1

Validation Targets

make gate          # Full 3-minute gate: validate + lint + test
make validate      # SKILL.md contract validation
make lint          # Reference URL liveness check
make test          # Pytest smoke tests
make check         # Freshness: hash drift detection

Review Checklist (per skill or implementation)

SKILL.md frontmatter valid and complete
All reference URLs resolve (HTTP 200)
Content hashes match stored values (or drift documented)
Acceptance criteria from HLD or feature doc explicitly met
No secrets, credentials, or API keys in any committed file
Coverage matrix updated to reflect current status
plugin.yaml reflects the skill if it's first-wave
Smoke tests pass for the affected skill