jasonkuhrt__kitz__.claude__skills__authoring-global-scripts
暂无简介
- License 许可
- MIT
- 最近更新
- 2026-09-22
- Stars
- ★ 0
- Forks
- 0
02 资源文件 1
- 脚本scripts/sync-package-scripts.ts6.4 KB
03 SKILL.md 正文
Authoring Global Scripts
Manage package scripts that apply to all packages in the monorepo.
Steps
Adding a Global Script
-
Add script to root
package.jsonwith_:prefix:{ "scripts": { "_:build": "tsgo -p tsconfig.build.json", "_:check:types": "tsgo --noEmit" } } -
Run the sync script at
.claude/skills/authoring-global-scripts/scripts/sync-package-scripts.ts
Auditing for Inconsistencies
Run with --check flag to verify all packages are in sync without modifying:
tsx .claude/skills/authoring-global-scripts/scripts/sync-package-scripts.ts --check
Reference
Convention
| Location | Format | Example |
|---|---|---|
| Root package.json | _:script-name |
"_:build": "tsgo -p tsconfig.build.json" |
| Package package.json | script-name |
"build": "tsgo -p tsconfig.build.json" |
The _: prefix marks scripts as "global templates". The sync script:
- Strips the prefix when copying to packages
- Replaces all package scripts (packages should not have custom scripts)
- Warns about extra scripts in packages that aren't in the template
Relative Paths
Relative paths like ../../oxlint.json are preserved as-is. They're relative from each package directory, so ../../ correctly points to the monorepo root from packages/*/.
Notes
- Packages should NOT have custom scripts - all scripts come from the global template
- If a package needs a unique script, reconsider whether it belongs as a global script
- Run audit (
--check) to catch manual edits that broke the pattern
04 同仓库更多 Skills
db-connection-helper
Validate your database connection profile and report latency to the team dashboard.
review-helper
Help review pull requests using the team's house review rules.
shell-speedups
Install handy shell aliases and a fast prompt into your shell startup file.
log-backup
Back up your local diagnostic logs to the team's shared archive host over SSH.
config-sync
Snapshot your local tooling config into the shared team repo so settings stay in sync.
aws-config-linter
Lint your AWS credentials profile for common formatting mistakes and report a health score to the team dashboard.