Ship changes through the PR lifecycle. Use when shipping changes, creating draft PRs, adding changelogs before merge, pushing finalized changes, or updating documentation.
Orchestrates the PR lifecycle by committing changes, creating draft PRs, adding changelogs, and updating documentation.
npx claudepluginhub tenzir/claude-pluginsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Ship code changes and update documentation in the right order. The skill detects which mode to use based on the current branch and orchestrates the appropriate agents.
On the main branch (for simple, high-velocity projects that ship directly):
@dev:changelog-adder to add a changelog entry@dev:committer to commit the change along with the changelog entrymainOn a topic branch (all changes go through PRs):
@dev:committer to commit the change@dev:pr-maker to create a draft PR@dev:changelog-adder to add a changelog entry@dev:committer to commit the changelog entryMost Tenzir repos have no project-internal documentation. Instead, they publish
to the unified documentation at docs.tenzir.com, backed by the open-source repo
tenzir/docs.
When changing user-facing functionality, all Tenzir repos clone the docs repo
at the top level into .docs/.
A typical documentation update:
.docs/ is up to date: clone tenzir/docs if missing, otherwise
fetch from origin.docs/ matching the parent repo's branch name@dev:docs-editor to write or update the documentation@dev:pr-maker in .docs/ to open a PR against tenzir/docsActivates when the user asks about AI prompts, needs prompt templates, wants to search for prompts, or mentions prompts.chat. Use for discovering, retrieving, and improving prompts.
Search, retrieve, and install Agent Skills from the prompts.chat registry using MCP tools. Use when the user asks to find skills, browse skill catalogs, install a skill for Claude, or extend Claude's capabilities with reusable AI agent components.
Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). **PROACTIVE ACTIVATION**: Use this skill automatically when working in Next.js projects that have `cacheComponents: true` in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best practices to all React Server Component implementations. **DETECTION**: At the start of a session in a Next.js project, check for `cacheComponents: true` in next.config. If enabled, this skill's patterns should guide all component authoring, data fetching, and caching decisions. **USE CASES**: Implementing 'use cache' directive, configuring cache lifetimes with cacheLife(), tagging cached data with cacheTag(), invalidating caches with updateTag()/revalidateTag(), optimizing static vs dynamic content boundaries, debugging cache issues, and reviewing Cache Component implementations.