Profile My skills Saved Collections Edit profile Submit a skill

← all publishers

lorem-dev

@lorem-dev source repo

8 published skills

  1. ▌
    Check Docs · lorem-dev
    Verify that the docs/ site, README.md, and CHANGES.md are current with the code: nav links resolve, documented commands and options still exist, and version references match the current version in package.json.
    0
    installs
  2. ▌
    Bump Version · lorem-dev
    Set the monorepo version across all package.json files and promote the CHANGES.md Development section to a released Version section, then create the release commit. Does not tag or push.
    0
    installs
  3. ▌
    Check Changes · lorem-dev
    Verify that CHANGES.md (Development section) reflects every commit since the last release. Flag missing entries, stale entries, over-long entries, or commits that have no corresponding changelog bullet.
    0
    installs
  4. ▌
    Check Licenses · lorem-dev
    Enumerate direct dependencies from every Cargo.toml and package.json, check each license against the acceptable/unacceptable list in CONTRIBUTING.md, update the Third-Party Notices section of LICENSE, and fail if any dependency carries a disallowed license.
    0
    installs
  5. ▌
    Check Glibc Floor · lorem-dev
    Verify the Linux glibc floor is consistent everywhere it is stated: the release workflow's runner image is the source of truth, and scripts/install.sh, docs/, and the release download labels must all agree with it. Also confirms the statically linked musl CLI is still built and published.
    0
    installs
  6. ▌
    Pre Release Check · lorem-dev
    Gate a release by running check-changes, check-docs, run-tests-and-linters, check-licenses, check-fixture-repo, and check-glibc-floor, plus verifying the version bump and that all commits since the last release follow the conventional-commits format.
    0
    installs
  7. ▌
    Check Fixture Repo · lorem-dev
    Validate the examples/test-repo fixture submodule and drive the built CLI against it end to end -- resolution schemes, groups, hooks, guidance precedence, executables, skill dependencies and `repo lint`, MCP presets and parameters, and the verify/repair round-trip -- in a throwaway state directory that cannot touch the developer's real configuration.
    0
    installs
  8. ▌
    Run Tests And Linters · lorem-dev
    Install dependencies, run the Rust gates (cargo fmt, clippy, test) and the TypeScript gates (ESLint, tsc typecheck, Vitest with v8 coverage at 90%, and the renderer Vite build). Report any failures clearly with file paths and line numbers.
    0
    installs