package-development

Agent Skills › krl-gr/upcomputer › package-development

package-development

GitHub

指导软件包注册、发布及维护的标准流程。涵盖工作区包添加、私有包发布、重命名及路径迁移，确保文件结构、依赖配置、代码生成和测试验证符合规范。

.repos/effect-smol/.agents/skills/package-development/SKILL.md krl-gr/upcomputer

Trigger Scenarios

添加工作区包发布私有包重命名软件包移动软件包工作区路径

Install

npx skills add krl-gr/upcomputer --skill package-development -g -y

More Options

Non-standard path

npx skills add https://github.com/krl-gr/upcomputer/tree/main/.repos/effect-smol/.agents/skills/package-development -g -y

Use without installing

npx skills use krl-gr/upcomputer@package-development

指定 Agent (Claude Code)

npx skills add krl-gr/upcomputer --skill package-development -a claude-code -g -y

安装 repo 全部 skill

npx skills add krl-gr/upcomputer --all -g -y

预览 repo 内 skill

npx skills add krl-gr/upcomputer --list

SKILL.md

Frontmatter

{
    "name": "package-development",
    "description": "Package registration. Use when adding a workspace package, making a private package publishable, renaming a package, or moving its workspace path."
}

Treat package work as a registration change, not a directory copy.

Workflow

Inspect the closest package in the same family. Classify publication status, runtime, test environment, platform support, barrels, and dependency shape. Justify each proposed file by precedent or an explicit repository need. Continue when every proposed file is justified.
Create or move only required source, test, TypeScript, and manifest files. When manifest dependencies change, read dependencies.md and classify every entry by role. Continue when pnpm discovers the intended name and manifests reference no absent file.
Read registration.md. Classify every registration surface as applicable or not applicable and update every applicable surface. Continue when every surface is classified and old references are explained.
For a published package, read publishing.md and verify its development and packed surfaces.
Run codegen when the package owns generated barrels, then inspect generated sections rather than editing them manually. Continue when generated sections match source modules without manual edits.
Run focused package tests and scripts plus applicable root checks. Include public API type tests when applicable. For published packages, build and dry pack the package as described in publishing.md. Continue when focused and root checks pass and the packed surface is intended.
Apply root changeset, generated-file, documentation, and workflow routing.

The task is complete when package discovery, registration, generated output, validation, packed output, and changeset routing are all verified or reported as not applicable.