.agents/skills/release-teamcopilot-npm

分类: 工具与效率 | 上传者: rishabhpoddar | 下载: 0 | 版本: v1.0（最新）

在 package.json 中确认发布版本后，将此存储库作为 TeamCopilot 发布到 npm。当用户想要为此存储库试运行、验证或发布新的 npm 版本时，请使用此选项。

更新日志: Source: GitHub https://github.com/rishabhpoddar/teamcopilot

目录结构

当前层级: tree/main/.agents/skills/release-teamcopilot-npm/

📁 scripts/
- 📄 publish.sh 2.4 KB
📄 SKILL.md 4.9 KB

SKILL.md

---
name: .agents/skills/release-teamcopilot-npm
description: Publish this repository to npm as TeamCopilot after confirming the release version in package.json. Use this when the user wants to dry-run, verify, or publish a new npm release for this repo.
---

# Release TeamCopilot npm

Use this skill when the task is to release the TeamCopilot package to npm from this repository.

This skill assumes `package.json` already contains the intended release version. Do not invent or bump the version inside this skill unless the user explicitly asks for that.

The release must stop if the version in `package.json` and `package-lock.json` do not match.

## Workflow

1. Read [package.json](../package.json) and confirm the current `name` and `version`.
2. Make sure the working tree is in a state suitable for release (git status is clean and on main branch). Do not hide or discard unrelated user changes.
3. Run the release helper:
   `./.agents/skills/release-teamcopilot-npm/scripts/publish.sh`
4. By default, prefer a dry run first:
   `./.agents/skills/release-teamcopilot-npm/scripts/publish.sh --dry-run`
5. If the dry run is clean and the user wants the real release, publish from the same commit.
6. When the `trythisapp` npm account requires TOTP, ask for a fresh authenticator code only after the dry run has passed, then run:
   `./.agents/skills/release-teamcopilot-npm/scripts/publish.sh --publish --skip-checks --otp <fresh-code>`
7. If TOTP is not required for the publish path, run:
   `./.agents/skills/release-teamcopilot-npm/scripts/publish.sh --publish`
8. After a successful publish, create a Git tag that exactly matches the package version, for example `0.0.1`.
9. Use `gh` to create a GitHub release for that tag with detailed manual release notes based on the changes since the previous release. Do not rely on GitHub autogenerated notes as the final release notes.

## What The Script Does

- Reads the package `name` and `version` from the repo root `package.json`
- Shows the exact release target, for example `teamcopilot@0.0.1`
- Verifies `package.json` and `package-lock.json` have the same version
- Runs `npm whoami` and requires the result to be `trythisapp`
- Runs `npm run test` and requires it to pass
- Runs `npm run build`
- Requires `npm run build` to pass
- Runs `npm pack --json`
- Deletes the generated `.tgz` after verification so the repo is not left dirty
- Publishes with `npm publish` only when `--publish` is passed
- Accepts `--otp <code>` and passes it through to `npm publish`
- Accepts `--skip-checks` to skip test/build/pack after a successful dry run on the same commit
- Accepts `--tag <tag>` and `--access public`
- After publish, GitHub tagging and release creation must be done separately with `gh`
- GitHub autogenerated notes may be used as reference material, but the final published release body must be written or edited manually

## Rules

- Treat the `package.json` version as the source of truth for the release version.
- Stop if `package-lock.json` does not have the same version.
- Prefer `--dry-run` before `--publish`.
- For the `trythisapp` account, prefer `--dry-run` first, then use `--publish --skip-checks --otp <fresh-code>` so the TOTP code is entered immediately before publish.
- Do not publish if tests fail.
- Do not publish if build fails.
- If `npm whoami` is not `trythisapp`, stop immediately.
- If the user wants a prerelease tag like `beta`, pass `--tag beta`.
- If the package ever becomes scoped, use `--access public` when required.
- After a successful npm publish, create a git tag equal to the package version with no prefix.
- Write detailed manual release notes that summarize the user-visible changes, important implementation details, and any caveats.
- Do not leave the release with only `--generate-notes` output or only the default compare link.
- If you use `gh release create <version> --generate-notes` as a starting point, immediately replace or edit the body with manual release notes before finishing.
- Push the tag or let `gh release create` create it from the current HEAD, but the final GitHub tag must exactly match the version in `package.json`.

## Examples

- Dry run the next release:
  `Use $.agents/skills/release-teamcopilot-npm to dry-run the npm release for this repo.`
- Publish the current version:
  `Use $.agents/skills/release-teamcopilot-npm to publish the current package.json version to npm.`
- Publish with a fresh TOTP code after a clean dry run:
  `Use $.agents/skills/release-teamcopilot-npm to publish this version from the trythisapp npm account with a fresh authenticator code, then create the matching GitHub release.`
- Publish a beta tag:
  `Use $.agents/skills/release-teamcopilot-npm to publish this version to npm with the beta tag.`
- Publish and create the GitHub release:
  `Use $.agents/skills/release-teamcopilot-npm to publish this version and then create the matching GitHub tag and release notes.`

## Resources

- `scripts/publish.sh`: deterministic npm release helper for this repo

登录后下载/点赞/收藏 ❤ 6 | ★ 0

.agents/skills/release-teamcopilot-npm

目录结构

SKILL.md

举报内容

提示