sync-convex-auth

Name: sync-convex-auth
Availability: InStock
Author: Udecode

Audit convex-better-auth diffs and delegate a focused implementation PR.

434|33|Updated Jul 27, 2025

Search Tags:#automation #diff #sync #auth #convex #pull-request #upstream

Ready to run

npx skills add https://github.com/udecode/kitcn --skill sync-convex-auth

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sync-convex-auth
Source: https://github.com/udecode/kitcn/tree/main/.agents/skills/sync-convex-auth
Command: npx skills add https://github.com/udecode/kitcn --skill sync-convex-auth

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sync kitcn against upstream changes in convex-better-auth by auditing commits, identifying relevant updates, and preparing a focused implementation PR through the task pipeline.

Core Features & Use Cases

Establish Fork, Upstream, And Refs: resolve fork/upstream metadata and track behind/ahead counts.
Read The Upstream Diff: inspect diffs to identify kitcn-relevant changes affecting auth integration.
Classify And Delegate: map changes to a chosen implementation slice and delegate via the task mechanism to open a PR.
This tool is used whenever kitcn auth surfaces require coordinated upstream alignment or security/tuning.

Quick Start

Invoke this skill to audit upstream convex-better-auth changes and delegate an implementation PR via the task system.

Frequently Asked Questions about sync-convex-auth

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

FAQPage Schema

How do I sync auth integration changes from an upstream repository?▼

Convex-better-auth upstream changes are synchronized by reading upstream diffs, classifying commits by relevance to your auth integration, and delegating a chosen implementation slice through the task workflow to open a pull request.

What is the best way to prepare a focused pull request for upstream auth updates?▼

Preparing a focused pull request involves mapping classified upstream diffs to a high-impact implementation slice and delegating it via the task mechanism. This ensures only relevant auth changes are applied rather than merging the entire upstream history.

Can I use this to track how far my fork is behind the upstream convex-better-auth repository?▼

Yes, you can use this to track how far your fork is behind the upstream repository. It resolves fork and upstream metadata to calculate behind and ahead counts before reading the upstream diff for auth integration changes.

When do I need to synchronize my downstream build with upstream auth changes?▼

You need to synchronize downstream builds with upstream auth changes whenever your auth surfaces require coordinated alignment, security patches, or tuning updates from the upstream convex-better-auth repository to maintain integration stability.

How does the task workflow handle the implementation of upstream diffs?▼

The task workflow handles upstream diffs by classifying changes by relevance, choosing a high-impact implementation slice, and delegating the actual implementation through the task prompt to open a prepared pull request.