Packs

1 pack

Quarkus Release Pipeline

Install this pack to run build, static analysis, security scan, and diff review before a Quarkus release.

3 skills · pack

Results for “release-pack”

10 skills

clawhub-plugin-packager

Package skills into publishable plugin or bundle formats for ClawHub, Claude marketplace, and related runtimes. Use when: converting a skill into a plugin or release bundle, generating manifests, and assembling a release-ready upload directory. Not for standalone metadata optimization or deep security auditing.

competition-supply-chain

Traces software supply chain provenance from source to runtime, identifying divergence points in dependency resolution, build, packaging, and release pipelines.

12.8k · bundle

opensource-pipeline

Fork, sanitize, and package private projects for safe public release through a three-stage pipeline.

More results

wp-plugin-development

Use when developing WordPress plugins: architecture and hooks, activation/deactivation/uninstall, admin UI and Settings API, data storage, cron/tasks, security (nonces/capabilities/sanitization/escaping), and release packaging.

Builds a compact secret-safe repository pack for AI handoff, review, or large analysis; prefers Repomix when available.

release-marketingclaw-ci

Run, watch, debug, and summarize MarketingClaw full release CI, release checks, live provider gates, install/update proofs, and release-secret preflights.

projectious-work

pk-release-audit

Use the release-audit skill to run the pre-release validation sweep and print

clawhub-skill-optimizer

Optimize publish-ready SKILL.md packages across ClawHub, Claude, Hermes, and GitHub. Use when: refining naming, frontmatter, body structure, bilingual copy, and release-mode variants without changing runtime behavior. Not for plugin manifest generation or deep security auditing.

lucassantana-dev

Full dependency lifecycle composite — audit known vulnerabilities, triage by severity and breaking-change risk, upgrade targeted packages, verify tests pass, ship PR. Use monthly, before releases, or when dependency alerts are stacking. Never do a blanket upgrade; always triage first.

wordpress-router

Use when the user asks about WordPress codebases (plugins, themes, block themes, Gutenberg blocks, WP core checkouts) and you need to quickly classify the repo and route to the correct workflow/skill (blocks, theme.json, REST API, WP-CLI, performance, security, testing, release packaging).