claude-native

Detect new Claude Code releases and create GitHub tracking issues.

13|6|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/baekenough/second-brain --skill claude-native
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: claude-native
Source: https://github.com/baekenough/second-brain/tree/main/.claude/skills/claude-native
Command: npx skills add https://github.com/baekenough/second-brain --skill claude-native

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Claude Code releases can slip through the cracks, causing delayed responses and untracked versions. This skill monitors new Claude Code releases and automatically opens GitHub issues for each untracked version to preserve an auditable release-tracking workflow. It replaces the deprecated customclaw Airflow-based monitoring (deprecated 2026-03-18) to provide ongoing, automated release governance.

Core Features & Use Cases

  • Auto-track Claude Code releases and create GitHub issues for each new version to ensure visibility.
  • Open and link issues in the repository to maintain a centralized release-tracking board.
  • Use case: a software maintenance team wants to ensure every Claude Code release is observed and followed up with action items.

Quick Start

Detect new Claude Code releases and generate tracking issues.

Frequently Asked Questions about claude-native

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically track Claude Code releases and create GitHub issues?

To automatically track Claude Code releases, this skill detects new versions and opens GitHub issues for each untracked release, ensuring a centralized and auditable release-tracking board.

Can I backfill GitHub issues for older Claude Code releases that were missed?

Yes, you can use the manual backfill mode to generate GitHub issues for older, previously untracked Claude Code releases, ensuring historical versions are added to your audit trail.

How do I test automated release tracking without creating duplicate GitHub issues?

You can use the dry-run mode to detect untracked Claude Code releases and preview the output without actually creating any GitHub issues, controlling the scope and safety of the operation.

What is the best way to maintain an auditable workflow for Claude Code version updates?

Maintaining an auditable workflow involves automatically opening and linking GitHub issues for every new Claude Code release, replacing deprecated monitoring methods to preserve continuous release governance.

Does this automated release tracking replace deprecated Airflow monitoring for Claude Code?

Yes, this skill replaces the deprecated customclaw Airflow-based monitoring to provide ongoing, automated release governance by directly tracking new Claude Code versions and creating issues.