skills.rest
EdgeApp
EdgeAppOFFICIAL
Explore all skills by this author →
Website𝕏@edgewalletGitHub

cheese

Hard-reset test-prefixed git branches and force-push to trigger Jenkins builds.

1|Updated Mar 24, 2026
Search Tags:#automation#git#testing#dependencies#build#ci
One-click install
npx skills add https://github.com/EdgeApp/edge-dev-agents --skill cheese-edgeapp
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cheese
Source: https://github.com/EdgeApp/edge-dev-agents/tree/main/.cursor/skills/cheese
Command: npx skills add https://github.com/EdgeApp/edge-dev-agents --skill cheese-edgeapp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, yarn, git, and includes scripts (resource) components.

What problem does it solve?

This Skill solves the friction of testing GUI changes by automating the creation of test-specific build branches and handling complex dependency pinning without manual intervention.

Core Features & Use Cases

  • Automated Build Triggers: Hard-resets test branches to your current feature work and force-pushes to trigger Jenkins builds.
  • Dependency Pinning: Automatically packs unreleased dependency repositories into tarballs and injects them into the GUI build to ensure the test environment reflects your latest changes.
  • Use Case: When you need to verify a GUI feature that depends on unmerged changes in edge-core-js, use this skill to pin the core repo and trigger a test build in one command.

Quick Start

Ask the agent to perform a cheese build for the current branch with the core dependency pinned.

Frequently Asked Questions about cheese

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I trigger an automated Jenkins build for a test branch using git?▼

Jenkins build triggers are automated by hard-resetting test-prefixed git branches to a source reference and force-pushing them. This approach automatically initiates the CI pipeline without requiring manual build invocations.

How do I pin unreleased dependencies as local tarballs for a GUI build?▼

Unreleased dependencies are pinned by packing their repositories into local tarballs and injecting them into the GUI build configuration. This ensures the test environment accurately reflects your latest unmerged changes.

Do I need yarn and jq installed to manage edge-react-gui workspace dependencies?▼

Yes, yarn and jq are required alongside git to manage the edge-react-gui workspace. Yarn handles package management while jq performs the necessary dependency resolution during the automated build process.

What is the best way to test GUI changes that depend on unmerged edge-core-js updates?▼

Testing GUI changes with unmerged dependencies is best handled by packing the core repository into a tarball and triggering a test build. This pins the unreleased dependency and initiates the build pipeline in one command.

Why does dependency injection fail when running test builds on a remote server?▼

Remote server build compatibility requires packing unreleased dependency repositories into local tarballs before injection. Without packing them as local tarballs, the build server cannot resolve unmerged dependency changes correctly.

Related Skills

Explore More Software Engineering Skills→
johnnystefanjohnnystefan

link-workspace-packages

Link missing workspace dependencies in monorepos using npm, yarn, pnpm, or bun.

Community
Basic
stolostronstolostron
3

acm-jenkins-client

Read Jenkins build status, test results, and trigger builds.

Official
Intermediate
devswapnil1995devswapnil1995

link-workspace-packages

Link workspace packages to resolve monorepo dependency and module resolution issues.

Community
Intermediate
huseyindenizhuseyindeniz
15

deps-minor

Automate minor npm dependency updates with lint, test, and build validation.

Community
Intermediate