catchup-ecc

Fetch new commits from affaan-m/everything-claude-code since the last cursor.

2|Updated Dec 20, 2020
One-click install
npx skills add https://github.com/buvis/home --skill catchup-ecc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: catchup-ecc
Source: https://github.com/buvis/home/tree/main/.claude/skills/catchup-ecc
Command: npx skills add https://github.com/buvis/home --skill catchup-ecc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps you stay up-to-date with new changes in affaan-m/everything-claude-code by reading commit history since your last check and surfacing actionable ideas for adoption.

Core Features & Use Cases

  • Read and track ECC-related commits from the target repository since the last cursor.
  • Summarize changes and surface ideas worth adopting for your CLAUDE setup.
  • Use Case: If you need to quickly assess whether new ECC code changes affect your workflows, generate a concise adoption plan.

Quick Start

Run the catchup-ecc skill to fetch new commits since your cursor and surface actionable ECC changes.

Frequently Asked Questions about catchup-ecc

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

FAQPage Schema
How do I track new commits in a GitHub repository since my last check?

To track new commits since your last check, the skill reads repository history using the GitHub API and compares it against a local cursor file to surface only the latest changes. It requires a stable internet connection to fetch updates.

Can I automatically review GitHub commit history for my CLAUDE setup?

Yes, you can review GitHub commit history for your CLAUDE setup by running the skill to fetch new commits. It analyzes the changes and proposes adoption ideas tailored to your specific configuration.

What is the best way to surface actionable ideas from repository updates?

The best way to surface actionable ideas from repository updates is to summarize new code changes and evaluate their relevance to your workflow. This skill generates a concise adoption plan based on the surfaced commits.

Do I need a local cursor file to monitor ECC repository changes?

Yes, you need a local cursor file to monitor ECC repository changes. The skill uses this file to store your last check position, allowing it to identify and fetch only the new commits since that specific point.

How does commit review work with the GitHub API for tracking repository changes?

Commit review with the GitHub API works by querying the target repository for recent history and filtering out commits already processed. The skill then assesses these new commits to determine their impact on your setup.

What are the limitations of using a cursor file for GitHub commit tracking?

A limitation of using a cursor file for GitHub commit tracking is that it relies on a stable internet connection to access the GitHub API. If the cursor file is deleted or corrupted, the skill cannot determine the last check position.