# Pre Release Check

> >

- **Type:** Skill
- **Install:** `agentstack add skill-lorem-dev-skillkeeper-pre-release-check`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [lorem-dev](https://agentstack.voostack.com/s/lorem-dev)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** Apache-2.0
- **Upstream author:** [lorem-dev](https://github.com/lorem-dev)
- **Source:** https://github.com/lorem-dev/skillkeeper/tree/main/.agents/skills/pre-release-check
- **Website:** https://lorem-dev.github.io/skillkeeper/

## Install

```sh
agentstack add skill-lorem-dev-skillkeeper-pre-release-check
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# pre-release-check

Run the full release gate. All checks must pass before tagging a release.

## Steps

### 1. Run the five component skills

Run each skill in order and collect its result (PASS or FAIL with details):

1. **check-licenses** -- must run first because a license failure is the most
   fundamental blocker.
2. **run-tests-and-linters** -- lint, typecheck, and coverage at 90%.
3. **check-fixture-repo** -- drive the built CLI against the `examples/test-repo`
   fixture end to end. This is the only check that exercises the real binary
   against a real working tree, so it catches wiring regressions the unit tests
   (which run against an in-memory filesystem) cannot see.
4. **check-docs** -- README.md, docs/ nav, command accuracy, version refs.
5. **check-changes** -- CHANGES.md Development section vs. commit history.

If check-licenses, run-tests-and-linters, or check-fixture-repo fails, report the
failure and stop. The remaining checks can still be reported for completeness,
but a release must not proceed while tests, licenses, or the end-to-end run are
failing.

If the fixture submodule is not checked out, `check-fixture-repo` cannot run.
Initialize it (`git submodule update --init`) rather than skipping the check --
a release must not ship without an end-to-end pass.

### 2. Verify the version bump

- Read `version` from the root `package.json`.
- Confirm the same version appears in all workspace package `package.json`
  files that ship to npm (i.e., under `packages/`).
- Confirm `CHANGES.md` has a `## Version ` section that matches the
  version in `package.json`, OR that the developer has prepared the entry under
  `## Development` and it is ready to be promoted.
- If versions are inconsistent across packages, list the discrepancies.

### 3. Verify the tag will be accepted from this branch

```bash
git branch --show-current
node scripts/check-tag-branch.mjs v
```

A release candidate (`v-rc.`) is cut from `develop`; a final release
(`v`) is cut from `main`. Only RC tags may come from `develop`. The
release pipeline enforces this in its first job, so checking here turns a failed
release run into a one-second local answer.

If the intended tag is final and the current branch is `develop`, the release is
not ready: merge to `main` first, or cut an RC instead.

### 4. Verify conventional-commits format for commits since the last release

```bash
git log --oneline ..HEAD
```

For each commit subject, verify:
- Starts with a valid type prefix: `feat`, `fix`, `chore`, `docs`, `test`,
  `refactor`, `perf`, `ci`, `build`, or `release`, optionally followed by
  `(scope)` and a colon.
- Subject is under 72 characters.
- Contains no AI-tool mentions (no "Co-Authored-By: Claude", "Co-Authored-By:
  Codex", "generated by", "with the help of AI", or similar).

Report each non-conforming commit with its hash and the specific violation.

### 5. Report

Produce a release-readiness summary:

```
check-licenses:            PASS / FAIL
run-tests-and-linters:     PASS / FAIL
check-fixture-repo:        PASS / FAIL
check-docs:                PASS / FAIL
check-changes:             PASS / FAIL
tag provenance (branch):   PASS / FAIL
version bump consistent:   PASS / FAIL
conventional commits:      PASS / FAIL (N non-conforming commits)

Release gate: PASS / FAIL
```

If the gate is PASS, confirm: "All checks passed. The release may proceed."
If the gate is FAIL, list every blocking issue with enough detail for the
developer to act immediately. Do not tag or publish a release while any check
is failing.

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [lorem-dev](https://github.com/lorem-dev)
- **Source:** [lorem-dev/skillkeeper](https://github.com/lorem-dev/skillkeeper)
- **License:** Apache-2.0
- **Homepage:** https://lorem-dev.github.io/skillkeeper/

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-lorem-dev-skillkeeper-pre-release-check
- Seller: https://agentstack.voostack.com/s/lorem-dev
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.