opencode-skills-collection 4.0.53 → 4.0.54

package/bundled-skills/cc-skill-strategic-compact/SKILL.md

@@ -1,19 +1,65 @@
 ---
 name: cc-skill-strategic-compact
-description: "Development skill from everything-claude-code"
+description: "Prepare a verified checkpoint before condensing an agent conversation at a phase boundary. Use during long tasks when context is repetitive; preserves constraints, evidence, decisions and the next action."
 risk: none
 source: community
 date_added: "2026-02-27"
 ---
 
-# cc-skill-strategic-compact
+# Strategic Context Checkpoints
 
-Development skill skill.
+Condense context after a verified phase, with enough durable information to resume the same task. A tool-call count is only a reminder; it cannot measure context quality or decide when compaction is safe.
 
 ## When to Use
-This skill is applicable to execute the workflow or actions described in the overview.
+Use when exploration has finished, a tested milestone has landed, or a long conversation contains repeated or obsolete reasoning. Do not compact in the middle of an unresolved tool call, an unrecorded approval decision, or a failure whose exact evidence has not been captured.
+
+## Inputs and prerequisites
+
+- The user's current objective, accepted constraints and definition of done.
+- The current branch and source revision, local changes, relevant artifact paths and actual check results.
+- Running processes, pending tool calls, approvals or external blockers.
+- A host-supported context-compaction mechanism. This skill does not assume `/compact` exists in every client or manipulate internal context files.
+
+## Procedure
+
+1. Choose a phase boundary: discovery to implementation, implementation to verification, or one completed batch to the next. Preserve an unresolved failure's reproduction first.
+2. Reconcile task state with the filesystem and Git. Distinguish completed, uncommitted, planned and failed work.
+3. Produce the checkpoint below. Include exact commands, result summaries and paths needed to resume; omit copied logs and discarded hypotheses that no longer matter.
+4. Check that the next action is executable and that a new context would not repeat a merge, send a message twice, lose a constraint or overwrite unrelated work.
+5. Save only in an already authorized project artifact, or return the checkpoint in the conversation. Do not rewrite global memory or host configuration automatically.
+6. Use the client's supported compaction command if requested and available. On resumption, read the checkpoint and verify mutable state before continuing.
+
+## Checkpoint template
+
+```text
+Objective and done condition:
+User constraints and authorization boundaries:
+Source revision, branch and local changes:
+Completed outcomes with verification:
+Outstanding work and known failures:
+Running process/tool identifiers:
+Artifacts and exact paths needed next:
+Next action, expected result and fallback:
+```
+
+## Worked example
+
+For a search feature whose source PR merged while canonical synchronization is pending, preserve the source merge SHA, canonical PR number and expected generated files. Record tests as passed only for the revision actually tested. The next action is to verify the canonical PR and updated `main`; it is not to merge the source PR again. If a browser check still needs an unlocked desktop, keep that condition visible while continuing independent code review.
+
+Expected outcome: the next context resumes outstanding verification, preserves unrelated local edits and does not claim publication from a source merge.
+
+## Optional stateless reminder
+
+```bash
+bash skills/cc-skill-strategic-compact/suggest-compact.sh 50
+```
+
+The helper accepts an observed tool-call count and optional threshold (default 50), and prints a reminder at the threshold and every 25 calls after it. `COMPACT_TOOL_COUNT` and `COMPACT_THRESHOLD` can be supplied by an explicit caller adapter. It stores no counter, estimates no token usage and never performs compaction. With no count it exits quietly.
+
+Earlier versions incremented a shared user-state counter across unrelated sessions. That counter is no longer read or written; existing custom wrappers must pass a session count explicitly. Existing state files are left untouched. This skill does not install or edit a hook.
 
 ## Limitations
-- Use this skill only when the task clearly matches the scope described above.
-- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
-- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
+- A checkpoint preserves recorded evidence, not all conversation detail. Keep primary artifacts when exact bytes matter.
+- Counts are caller-provided, bounded non-negative decimal integers; reminders are not a context-capacity measurement.
+- Branches, processes and remote checks can change after a checkpoint. Revalidate them instead of treating a summary as current truth.
+- Client context management differs. Do not simulate compaction by deleting chat databases, logs, caches or project files.

package/bundled-skills/cc-skill-strategic-compact/suggest-compact.sh

@@ -1,54 +1,23 @@
-#!/bin/bash
-# Strategic Compact Suggester
-# Runs on PreToolUse or periodically to suggest manual compaction at logical intervals
-#
-# Why manual over auto-compact:
-# - Auto-compact happens at arbitrary points, often mid-task
-# - Strategic compacting preserves context through logical phases
-# - Compact after exploration, before execution
-# - Compact after completing a milestone, before starting next
-#
-# Hook config (in ~/.claude/settings.json):
-# {
-#   "hooks": {
-#     "PreToolUse": [{
-#       "matcher": "Edit|Write",
-#       "hooks": [{
-#         "type": "command",
-#         "command": "~/.claude/skills/strategic-compact/suggest-compact.sh"
-#       }]
-#     }]
-#   }
-# }
-#
-# Criteria for suggesting compact:
-# - Session has been running for extended period
-# - Large number of tool calls made
-# - Transitioning from research/exploration to implementation
-# - Plan has been finalized
-
-# Track tool call count in a user-owned state directory
-COUNTER_DIR="${XDG_STATE_HOME:-$HOME/.local/state}/strategic-compact"
-mkdir -p "$COUNTER_DIR"
-COUNTER_FILE="$COUNTER_DIR/tool-count"
-THRESHOLD=${COMPACT_THRESHOLD:-50}
-
-# Initialize or increment counter
-if [ -f "$COUNTER_FILE" ]; then
-  count=$(cat "$COUNTER_FILE")
-  count=$((count + 1))
-  echo "$count" > "$COUNTER_FILE"
-else
-  echo "1" > "$COUNTER_FILE"
-  count=1
+#!/usr/bin/env bash
+# Stateless reminder using a caller-supplied session count. Never compacts or saves.
+set -euo pipefail
+if [ "$#" -gt 2 ]; then
+  echo 'Usage: suggest-compact.sh [tool-count [threshold]]' >&2
+  exit 2
 fi
-
-# Suggest compact after threshold tool calls
-if [ "$count" -eq "$THRESHOLD" ]; then
-  echo "[StrategicCompact] $THRESHOLD tool calls reached - consider /compact if transitioning phases" >&2
+count="${1:-${COMPACT_TOOL_COUNT:-}}"
+[ -n "$count" ] || exit 0
+threshold="${2:-${COMPACT_THRESHOLD:-50}}"
+if [[ ! "$count" =~ ^[0-9]{1,6}$ ]] || [[ ! "$threshold" =~ ^[0-9]{1,6}$ ]]; then
+  echo '[StrategicCompact] Count and threshold must be bounded decimal integers.' >&2
+  exit 2
 fi
-
-# Suggest at regular intervals after threshold
-if [ "$count" -gt "$THRESHOLD" ] && [ $((count % 25)) -eq 0 ]; then
-  echo "[StrategicCompact] $count tool calls - good checkpoint for /compact if context is stale" >&2
+count=$((10#$count))
+threshold=$((10#$threshold))
+if [ "$threshold" -lt 1 ]; then
+  echo '[StrategicCompact] Threshold must be positive.' >&2
+  exit 2
+fi
+if [ "$count" -ge "$threshold" ] && [ $(((count - threshold) % 25)) -eq 0 ]; then
+  echo "[StrategicCompact] $count tool calls; prepare a verified checkpoint if this phase has finished. Nothing compacted or saved." >&2
 fi

package/bundled-skills/changelog-updates/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: changelog-updates
-description: 'Create release notes and product updates that developers actually read and care about. This skill covers changelog formatting, versioning communication, breaking change announcements, deprecation notices, and building anticipation for new features. Trigger phrases: "changelog",...'
+description: "Create release notes and product updates that developers actually read and care about. This skill covers changelog formatting, versioning communication, breaking change announcements, deprecation notices, and building anticipation for new features."
 risk: critical
 source: https://github.com/jonathimer/devmarketing-skills/tree/main/skills/changelog-updates
 source_repo: jonathimer/devmarketing-skills
@@ -11,539 +11,17 @@ license_source: https://github.com/jonathimer/devmarketing-skills/blob/main/LICE
 ---
 
 # Changelogs and Product Updates Developers Care About
-## When to Use
-
-Use this skill when you need create release notes and product updates that developers actually read and care about. This skill covers changelog formatting, versioning communication, breaking change announcements, deprecation notices, and building anticipation for new features. Trigger phrases: "changelog",...
-
-
-Release notes are developer communication, not documentation. When done well, they build trust, demonstrate momentum, and turn updates into marketing moments.
-
-## Overview
-
-Changelogs serve multiple audiences and purposes:
-- **Active developers**: "What changed that affects my integration?"
-- **Evaluating developers**: "Is this product actively maintained?"
-- **Developer advocates**: "What's worth sharing with my audience?"
-- **Your team**: Historical record of what shipped and when
-
-This skill covers creating changelogs that inform, build trust, and occasionally delight.
-
-## Before You Start
-
-Review the **developer-audience-context** skill to understand:
-- How do your developers prefer to receive updates?
-- What changes do they care most about?
-- How much detail do they need?
-- What's their tolerance for breaking changes?
-
-Your changelog tone and detail level should match your audience.
-
-## Changelog Format
-
-### The Standard Structure
-
-```markdown
-# Changelog
-
-All notable changes to this project will be documented in this file.
-
-The format is based on [Keep a Changelog](https://keepachangelog.com/),
-and this project adheres to [Semantic Versioning](https://semver.org/).
-
-## [Unreleased]
-### Added
-- New feature in development
-
-## [2.3.0] - 2024-01-15
-### Added
-- New `analyze()` method for sentiment analysis
-- Support for batch processing up to 100 items
-
-### Changed
-- Improved error messages with troubleshooting links
-- Default timeout increased from 30s to 60s
-
-### Deprecated
-- `old_analyze()` will be removed in v3.0.0
-
-### Fixed
-- Race condition in concurrent requests (#234)
-- Memory leak when processing large files (#256)
-
-## [2.2.1] - 2024-01-08
-### Fixed
-- Critical security patch for authentication bypass
-
-## [2.2.0] - 2024-01-01
-...
-```
-
-### Change Categories
-
-| Category | Use For |
-|----------|---------|
-| **Added** | New features, new endpoints, new parameters |
-| **Changed** | Behavior changes, performance improvements |
-| **Deprecated** | Features being phased out (still working) |
-| **Removed** | Features that no longer exist |
-| **Fixed** | Bug fixes |
-| **Security** | Security-related changes |
-
-### Good vs. Bad Entries
-
-**Good Changelog Entries:**
-```markdown
-### Added
-- New `batch_analyze()` method processes up to 100 items in a single
-  request, reducing API calls by 90% for bulk operations.
-  [See docs](https://github.com/jonathimer/devmarketing-skills/tree/main/skills/changelog-updates/link) (#198)
-
-### Fixed
-- Fixed timeout errors when processing files larger than 10MB.
-  Uploads now stream in chunks, eliminating memory issues. (#234)
-
-### Deprecated
-- `legacy_auth()` will be removed in v3.0.0 (scheduled for March 2024).
-  Migrate to `oauth_auth()` using our [migration guide](https://github.com/jonathimer/devmarketing-skills/tree/main/skills/changelog-updates/link).
-```
-
-**Bad Changelog Entries:**
-```markdown
-### Added
-- New feature
-
-### Fixed
-- Fixed bug
-- Fixed another bug
-- Various improvements
-
-### Changed
-- Updated dependencies
-```
-
-### Writing Style
-
-**Be specific:**
-```
-❌ "Improved performance"
-✅ "Reduced API response time by 40% for list operations"
-```
-
-**Include context:**
-```
-❌ "Fixed issue #234"
-✅ "Fixed timeout errors when uploading large files (#234)"
-```
-
-**Link to resources:**
-```
-✅ "New batch API - [documentation](https://github.com/jonathimer/devmarketing-skills/tree/main/skills/changelog-updates/link) | [migration guide](https://github.com/jonathimer/devmarketing-skills/tree/main/skills/changelog-updates/link)"
-```
-
-**Explain impact:**
-```
-✅ "Breaking: `user_id` parameter renamed to `id`.
-    Update your code before upgrading."
-```
-
-## What to Include
-
-### Always Include
-
-**API Changes:**
-- New endpoints
-- New parameters
-- Changed response formats
-- Changed error codes
-
-**SDK Changes:**
-- New methods
-- Changed method signatures
-- New configuration options
-
-**Breaking Changes:**
-- Anything that requires code changes
-- Removed features
-- Changed defaults
-
-**Security Fixes:**
-- Even if vague, acknowledge security updates
-- Follow responsible disclosure timeline
-
-### Consider Including
-
-**Performance Improvements:**
-```markdown
-### Changed
-- List operations now 3x faster through pagination optimization
-```
-
-**Developer Experience:**
-```markdown
-### Added
-- Error messages now include troubleshooting links
-- SDK now validates API keys at initialization
-```
-
-**Infrastructure:**
-```markdown
-### Changed
-- New data center in EU (eu-west.api.example.com)
-- Increased rate limits from 100 to 500 requests/minute
-```
-
-### Skip or Minimize
-
-**Internal refactoring:**
-```markdown
-❌ "Refactored authentication module"
-(unless it affects developers)
-```
-
-**Minor dependency updates:**
-```markdown
-❌ "Updated lodash from 4.17.20 to 4.17.21"
-(unless security-related)
-```
-
-**Typo fixes:**
-```markdown
-❌ "Fixed typo in error message"
-(batch these into "Various documentation improvements")
-```
-
-## Versioning Communication
-
-### Semantic Versioning Explained to Users
-
-Help developers understand what version numbers mean:
-
-```markdown
-# Versioning
-
-We follow [Semantic Versioning](https://semver.org/):
-
-- **Major versions (3.0.0)**: May include breaking changes.
-  Check the migration guide before upgrading.
-
-- **Minor versions (2.3.0)**: New features, backward compatible.
-  Safe to upgrade.
-
-- **Patch versions (2.3.1)**: Bug fixes only.
-  Always safe to upgrade.
-```
-
-### Version Pinning Guidance
-
-Help developers make good choices:
-
-```markdown
-# Recommended Version Constraints
-
-For stability, we recommend:
-- `"myapi": "^2.3.0"` - Get patches and minor updates
-- `"myapi": "~2.3.0"` - Get patches only
-
-For production systems:
-- Pin exact versions: `"myapi": "2.3.0"`
-- Review changelogs before upgrading
-- Test in staging first
-```
-
-### API Versioning Communication
-
-```markdown
-# API Versions
-
-## Current Versions
-- **v2** (current): Full support, recommended for new integrations
-- **v1** (legacy): Security fixes only, sunset March 2025
 
-## Version Lifecycle
-| Status | Duration | What It Means |
-|--------|----------|---------------|
-| Current | Ongoing | Full support, new features |
-| Legacy | 12 months | Security fixes only |
-| Deprecated | 6 months | No updates, migration required |
-| Sunset | - | No longer available |
+## Detailed Guide
 
-## Specifying Version
-```bash
-curl https://api.example.com/v2/users
-# or
-curl -H "API-Version: 2024-01-15" https://api.example.com/users
-```
-```
+Read [the detailed guide](references/detailed-guide.md) before executing this skill. It retains the complete procedure and reference material. Treat its safety, prerequisites, and validation requirements as mandatory. For focused work, load the relevant sections; for end-to-end work, read the guide completely.
 
-## Breaking Changes
-
-### Breaking Change Announcement Template
-
-```markdown
-# Breaking Change: [Brief Description]
-
-**Affects**: SDK v3.0.0, API version 2024-03
-**Timeline**: Changes take effect March 15, 2024
-
-## What's Changing
-[Clear description of the change]
-
-## Why We're Making This Change
-[Honest explanation - better performance, security, consistency]
-
-## Who's Affected
-- ✅ Users of SDK v2.x - no action required
-- ⚠️ Users of SDK v3.0.0+ - update required
-- ⚠️ Direct API users on v1 - update required
-
-## Required Actions
-
-### If you use our SDK:
-```python
-# Before (v2.x)
-client.old_method(user_id="123")
-
-# After (v3.x)
-client.new_method(id="123")
-```
-
-### If you call the API directly:
-```bash
-# Before
-POST /v1/users/123/analyze
-
-# After
-POST /v2/users/123/analyze
-```
-
-## Migration Guide
-[Link to detailed migration documentation]
-
-## Timeline
-- **Now**: v3.0.0 beta available for testing
-- **Feb 1**: v3.0.0 stable released
-- **Mar 1**: v2.x enters legacy support
-- **Mar 15**: Breaking changes take effect in API
-- **Sep 15**: v2.x sunset (no longer supported)
-
-## Need Help?
-- [Migration guide](https://github.com/jonathimer/devmarketing-skills/tree/main/skills/changelog-updates/link)
-- [Office hours signup](https://github.com/jonathimer/devmarketing-skills/tree/main/skills/changelog-updates/link)
-- [Support channel](https://github.com/jonathimer/devmarketing-skills/tree/main/skills/changelog-updates/link)
-```
-
-### Breaking Change Communication Timeline
-
-```
-6 months before:  Announce upcoming change
-3 months before:  Release new version with migration path
-1 month before:   Send direct emails to affected users
-2 weeks before:   Final reminder
-Day of:           Change takes effect
-1 week after:     Follow-up for stragglers
-```
-
-## Deprecation Notices
-
-### In-Code Deprecation
-
-```python
-import warnings
-
-def old_method(self, user_id):
-    """
-    .. deprecated:: 2.3.0
-       Use :meth:`new_method` instead. Will be removed in v3.0.0.
-    """
-    warnings.warn(
-        "old_method() is deprecated and will be removed in v3.0.0. "
-        "Use new_method() instead. "
-        "Migration guide: https://docs.example.com/migrate-v3",
-        DeprecationWarning,
-        stacklevel=2
-    )
-    return self.new_method(id=user_id)
-```
-
-### API Deprecation Headers
-
-```http
-HTTP/1.1 200 OK
-Deprecation: Sun, 15 Sep 2024 00:00:00 GMT
-Sunset: Sun, 15 Mar 2025 00:00:00 GMT
-Link: <https://docs.example.com/migrate-v3>; rel="deprecation"
-
-{
-  "data": {...},
-  "_deprecation": {
-    "message": "This endpoint is deprecated",
-    "sunset": "2025-03-15",
-    "migration": "https://docs.example.com/migrate-v3"
-  }
-}
-```
-
-### Deprecation Changelog Entry
-
-```markdown
-### Deprecated
-- **`/v1/analyze` endpoint**: Use `/v2/analyze` instead.
-  - Migration guide: [link]
-  - Sunset date: March 15, 2025
-  - After sunset: Requests will return 410 Gone
-```
-
-## Building Anticipation
-
-### "Coming Soon" Announcements
-
-Build excitement for upcoming features:
-
-```markdown
-# Coming in Q2 2024
-
-## Batch Processing API (Beta available now)
-Process up to 1,000 items in a single request.
-[Join the beta](https://github.com/jonathimer/devmarketing-skills/tree/main/skills/changelog-updates/link)
-
-## Python SDK v3.0
-Complete rewrite with async support, type hints, and 50% faster.
-[Preview documentation](https://github.com/jonathimer/devmarketing-skills/tree/main/skills/changelog-updates/link)
-
-## EU Data Residency
-For customers with European data requirements.
-[Join waitlist](https://github.com/jonathimer/devmarketing-skills/tree/main/skills/changelog-updates/link)
-```
-
-### Release Cadence Communication
-
-Set expectations:
-
-```markdown
-# Release Schedule
-
-**SDK Releases**: First Monday of each month
-**API Updates**: Continuous (backward compatible)
-**Breaking Changes**: Twice per year (March, September)
-
-Subscribe to updates:
-- [GitHub releases](https://github.com/jonathimer/devmarketing-skills/tree/main/skills/changelog-updates/link)
-- [Email newsletter](https://github.com/jonathimer/devmarketing-skills/tree/main/skills/changelog-updates/link)
-- [Discord announcements](https://github.com/jonathimer/devmarketing-skills/tree/main/skills/changelog-updates/link)
-- [Twitter/X](https://github.com/jonathimer/devmarketing-skills/tree/main/skills/changelog-updates/link)
-```
-
-### Feature Launches as Events
-
-Turn significant releases into moments:
-
-```markdown
-# 🚀 SDK v3.0 Launch
-
-We're excited to announce the biggest SDK update in 2 years!
-
-## Highlights
-- **50% faster** request processing
-- **Full async support** for high-throughput applications
-- **Type hints** throughout for better IDE support
-- **Simplified auth** - configure once, use everywhere
-
-## Launch Week
-- **Monday**: SDK v3.0 stable release
-- **Tuesday**: Live coding session (YouTube)
-- **Wednesday**: Migration office hours
-- **Thursday**: Community showcase
-- **Friday**: AMA with the SDK team
-
-## Resources
-- [Documentation](https://github.com/jonathimer/devmarketing-skills/tree/main/skills/changelog-updates/link)
-- [Migration guide](https://github.com/jonathimer/devmarketing-skills/tree/main/skills/changelog-updates/link)
-- [Video walkthrough](https://github.com/jonathimer/devmarketing-skills/tree/main/skills/changelog-updates/link)
-
-## Thank You
-Special thanks to our 47 beta testers who found 23 bugs
-and suggested 12 improvements that made it into this release!
-```
-
-## Distribution Channels
-
-### Where to Publish
-
-| Channel | Audience | Content Level |
-|---------|----------|---------------|
-| GitHub Releases | Developers on repo | Full changelog |
-| Docs changelog | All developers | Full changelog |
-| Blog | Broader audience | Highlights + context |
-| Email | Active users | Summary + action items |
-| Twitter/X | Community | Highlights only |
-| Discord/Slack | Engaged community | Discussion + highlights |
-
-### Email Templates
-
-**Regular Release:**
-```
-Subject: [Product] v2.3.0 Released - Batch Processing + Bug Fixes
-
-Hey [name],
-
-We just released v2.3.0 with some improvements you'll like:
-
-✨ New batch processing API - handle 100 items at once
-🐛 Fixed timeout issues with large files
-⚡ 40% faster list operations
-
-Full changelog: [link]
-Upgrade guide: [link]
-
-Happy building,
-The [Product] Team
-```
-
-**Breaking Change:**
-```
-Subject: ⚠️ Action Required: [Product] Breaking Change on March 15
-
-Hey [name],
-
-We're making changes to improve [X], and you'll need to
-update your integration before March 15.
-
-What's changing: [one sentence]
-What you need to do: [one sentence]
-Full details: [link]
-
-Need help? Reply to this email or join our office hours: [link]
-
-Best,
-The [Product] Team
-```
-
-## Tools
-
-### Changelog Generation
-- **Conventional Commits**: Structured commit messages
-- **semantic-release**: Automated changelog from commits
-- **changesets**: Monorepo changelog management
-- **Keep a Changelog**: Format specification
-
-### Distribution
-- **GitHub Releases**: Native to most developer workflows
-- **Beehiiv/Buttondown**: Developer newsletter platforms
-- **Twitter/X**: Quick updates to community
-- **Discord/Slack**: Community discussions
+## When to Use
 
-### Monitoring
-- **GitHub Stars/Watchers**: Engagement metrics
-- **npm download stats**: Adoption tracking
-- **Email open rates**: Communication effectiveness
+Use this skill when you need create release notes and product updates that developers actually read and care about. This skill covers changelog formatting, versioning communication, breaking change announcements, deprecation notices, and building anticipation for new features. Trigger phrases: "changelog",...
 
-## Related Skills
 
-- **sdk-dx**: SDK versioning and migration
-- **docs-as-marketing**: Changelog as documentation
-- **developer-community**: Community communication channels
-- **developer-metrics**: Measuring changelog engagement
-- **technical-content-strategy**: Changelog as content
+Release notes are developer communication, not documentation. When done well, they build trust, demonstrate momentum, and turn updates into marketing moments.
 
 ## Limitations