Agent Skills › t4t5/rencal › local-caldir

local-caldir

GitHub

指导开发者将 renCal 指向本地 caldir 源码进行开发测试，支持验证未发布的 core 或 provider 变更。通过构建本地 provider 和配置 Cargo 路径补丁实现，并提供恢复至固定版本的清理步骤。

.agents/skills/local-caldir/SKILL.md t4t5/rencal

Trigger Scenarios

用户希望测试未发布的 caldir-core 变更用户要求使用本地 caldir 目录用户指示点按本地 caldir checkout

Install

npx skills add t4t5/rencal --skill local-caldir -g -y

More Options

Non-standard path

npx skills add https://github.com/t4t5/rencal/tree/main/.agents/skills/local-caldir -g -y

Use without installing

npx skills use t4t5/rencal@local-caldir

指定 Agent (Claude Code)

npx skills add t4t5/rencal --skill local-caldir -a claude-code -g -y

安装 repo 全部 skill

npx skills add t4t5/rencal --all -g -y

预览 repo 内 skill

npx skills add t4t5/rencal --list

SKILL.md

Frontmatter

{
    "name": "local-caldir",
    "description": "Develop renCal against a local caldir checkout instead of the pinned release. Use when the user wants to test unreleased caldir-core or provider changes, or asks to \"use local caldir\" \/ \"point rencal at my caldir checkout\"."
}

Local caldir checkout

renCal pins caldir-core (crate) and the provider binaries (release tag) separately in src-tauri/Cargo.toml. To develop against a local checkout (../caldir by default):

Providers: just build-providers-local [path] builds them from the checkout into src-tauri/providers/.
caldir-core: create a gitignored .cargo/config.toml in the repo root that patches the crate (path is relative to the repo root):
```
[patch.crates-io]
caldir-core = { path = "../caldir/caldir-core" }
```
This rewrites src-tauri/Cargo.lock; do not commit that change.
Back to the pinned release: delete .cargo/config.toml and src-tauri/providers/. The next just dev re-downloads the pinned providers.