frontend-forge-fe-operations
Operate FrontendExtension (FE) resources in frontend-forge: create, update, rebuild, inspect package artifacts, download packages, publish, unpublish, delete, and debug package/publish controller behavior. Use this skill whenever the user mentions FE operations, FrontendExtension lifecycle, extension package/download/publish/unpublish, artifact ConfigMaps, package Jobs, publisher Jobs, publish target ConfigMaps or Secrets, rebuild-token, package-state/publish-state labels, or troubleshooting FE status in a Kubernetes cluster.
npx skills add kubesphere/kubesphere --skill frontend-forge-fe-operations --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Frontend Forge FE Operations ## When to use Use this skill for operational work around `FrontendExtension` resources: - Create or update an FE manifest - Trigger or inspect package generation - Force a rebuild with the rebuild-token annotation - Download the generated package artifact - Publish, unpublish, or delete an extension - Inspect FE status, conditions, labels, Jobs, artifact ConfigMaps, and publish targets - Debug FE package phases such as `Packaging`, `Ready`, and `Failed`, plus publish/unpublish phases such as `Pending`, `Running`, `Succeeded`, and `Failed` If the task is about `FrontendIntegration` runtime `JSBundle` creation, use the FI operations skill instead. FE package/publish does not create a runtime `JSBundle` in the current cluster. ## Quick Entry - Create or update FE -> read `references/lifecycle.md` - Rebuild package -> read `references/lifecycle.md` - Publish, unpublish, delete-with-unpublish, list through API, or download -> read `references/api.md` - Inspect package Job, artifact ConfigMap, publish Job, labels, or conditions -> read `references/inspection.md` - Debug stuck or failed state -> read `references/inspection.md`, then check controller logs ##
- When to use
- Quick Entry
- Preconditions
- Source of truth
- Resource Model
- Common Commands
- Operating Rules
- Safety Rules
- Status Fields To Check
- Troubleshooting Order
- Controller Logs
kubectl get fe <name> -o yaml
kubectl get fe <name> -o jsonpath='{.status}{"\n"}'
kubectl get fe <name> -o jsonpath='{.status.phase}{" "}{.status.publish.phase}{" "}{.status.unpublish.phase}{"\n"}'
kubectl get fe -l frontend-forge.kubesphere.io/package-state=ready
kubectl get fe -l frontend-forge.kubesphere.io/publish-state=published
kubectl apply -f <file.yaml>
kubectl apply -f config/samples/frontendextension-inspecttask.yaml
kubectl get fe <name> -o jsonpath='{.status.packageJob.namespace}{" "}{.status.packageJob.name}{"\n"}'
kubectl -n <job-namespace> get job <job-name> -o yaml
kubectl -n <job-namespace> logs job/<job-name>What does the frontend-forge-fe-operations skill do?
Operate FrontendExtension (FE) resources in frontend-forge: create, update, rebuild, inspect package artifacts, download packages, publish, unpublish, delete, and debug package/publish controller behavior. Use this skill whenever the user mentions FE operations, FrontendExtension lifecycle, extension package/download/publish/unpublish, artifact ConfigMaps, package Jobs, publisher Jobs, publish target ConfigMaps or Secrets, rebuild-token, package-state/publish-state labels, or troubleshooting FE status in a Kubernetes cluster.
How do I install it?
Run `npx skills add kubesphere/kubesphere --skill frontend-forge-fe-operations --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From kubesphere/kubesphere, a repository with 17,016 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.