Docs/changelog checkpoint. Detects whether changes are user-facing and ensures documentation hygiene (CHANGELOG + lessons-learned) is handled or explicitly bypassed. Use when: 'docs check', 'changelog', 'release notes', 'did we update docs?'.
Ensures documentation hygiene by checking for changelog updates or explicit bypass labels on code changes.
/plugin marketplace add ggprompts/tabzchrome/plugin install conductor@tabzchrome-marketplaceThis skill is limited to using the following tools:
Ensures documentation hygiene is not missed.
Writes result to .checkpoints/docs-check.json.
*.md, *.txt, or files under .claude/, .claude-plugin/, docs/, plugins/) → PASSCHANGELOG.md updated, ORno-changelogWhy the bypass label? Some changes are internal/refactors and not user-facing. The label makes that decision explicit and searchable.
You should be given an issue ID in the prompt (e.g. TabzChrome-abc).
Determine changed files:
git status --porcelain
# If clean, compare to main
git diff --name-only main...HEAD
# If not clean, prefer staged+unstaged
git diff --name-only
git diff --cached --name-only
CHANGED=$( (git diff --name-only main...HEAD 2>/dev/null || true) ; git diff --name-only 2>/dev/null || true ; git diff --cached --name-only 2>/dev/null || true )
CHANGED=$(echo "$CHANGED" | sed '/^$/d' | sort -u)
# Docs-only patterns (v1)
if echo "$CHANGED" | grep -qvE '(\.md|\.markdown|\.txt)$' \
&& echo "$CHANGED" | grep -qvE '^(docs/|plugins/|\.claude/|\.claude-plugin/)'; then
CODE_CHANGED=1
else
CODE_CHANGED=0
fi
If CODE_CHANGED=1, check:
# Changelog modified?
git diff --name-only main...HEAD 2>/dev/null | grep -q '^CHANGELOG\.md$' && CHANGELOG_OK=1 || CHANGELOG_OK=0
# Issue has bypass label?
LABELS=$(bd show "$ISSUE_ID" --json 2>/dev/null | jq -r '.[0].labels[]?' 2>/dev/null || true)
echo "$LABELS" | grep -qx 'no-changelog' && BYPASS=1 || BYPASS=0
CHANGELOG_OK=1 OR BYPASS=1 → PASSCHANGELOG.md entry or a no-changelog label.mkdir -p .checkpoints
cat > .checkpoints/docs-check.json << EOF
{
"checkpoint": "docs-check",
"timestamp": "$(date -Iseconds)",
"passed": ${PASSED},
"code_changed": ${CODE_CHANGED},
"changelog_updated": ${CHANGELOG_OK},
"bypass_label": ${BYPASS},
"summary": "${SUMMARY}"
}
EOF
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.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.