agentleFS
tuanductrantuanductran/hr-skills/.agents/skills/bun/SKILL.md

bun

Skill58 starsChanged 2 months agoMITView on GitHub

Repository guidance for using Bun as the runtime, package manager, and workspace toolchain within the hr-skills monorepo.

15 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use analytics-metrics, aws-account-management and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • hoodiniSkill

    analytics-metrics

    Build data visualization and analytics dashboards. Use when creating charts, KPI displays, metrics dashboards, or data visualization components. Triggers on analytics, dashboard, charts, metrics, KPI, data visualization, Recharts.

    Also in 3 projects that use this

  • hoodiniSkill

    aws-account-management

    Manage AWS accounts, organizations, IAM, and billing. Use when setting up AWS Organizations, managing IAM policies, controlling costs, or implementing multi-account strategies. Triggers on AWS Organizations, AWS IAM, AWS billing, Cost Explorer, SCPs, multi-account, AWS SSO, Identity Center.

    Also in 3 projects that use this

  • kelvincushmanSkill

    gh-commit

    Create well-formatted commits with conventional commit format.

    Also in 3 projects that use this

  • LangChainSkill

    langchain

    Build agents with a prebuilt architecture and integrations for any model or tool. Use when creating tool-calling agents, switching model providers, or adding structured output.

    Also in 4 projects that use this

  • kelvincushmanSkill

    prek

    Use when setting up or running hooks with prek in any repository. prek is a Rust drop-in alternative to pre-commit for running Git hooks that check, format, lint, and validate code and repository files. Prefer it when speed, workspace mode, built-in hooks, shared toolchains, or native TOML configuration matter.

    Also in 3 projects that use this

  • ant-designSkill

    gh-create-pr

    使用 GitHub CLI (gh) 推送当前分支并创建或更新 PR。在用户说「提 PR」「新建 PR」「用 gh 建 PR」「submit PR」「create pull request」时使用。

    Also in 3 projects that use this

  • +6 more from hoodini

The file

Show its rules and text

We split this skill into the rules it gives an agent

33 rules. 0 are common, 21 are distinctive, and 12 are very specific to this project.

  • 0

    Common

    Most of the 9 edited versions we read keep these.

  • 21

    Distinctive

    This author's own choices. Worth a look.

  • 12

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run repository scripts using Bun

    line 19
  2. Distinctive:

    Run tests and TypeScript type checking

    line 23
  3. Distinctive:

    Use the default catalog.

    line 52
  4. Distinctive:

    Use a named catalog.

    line 62
  5. Distinctive:

    When working in this repository:

    line 85
  6. Very specific:

    If a package works in Node.js but fails in Bun, treat it as a Bun compatibility issue rather than a repository issue.

    line 88
  7. Very specific:

    Prefer standard node: imports for built-in Node.js modules.

    line 89
  8. Distinctive:

    Prefer Bun-native APIs only when they provide a clear repository benefit.

    line 90
  9. Distinctive:

    Run all test suites.

    line 140
  10. Distinctive:

    Run TypeScript type checking.

    line 146
  11. Distinctive:

    Run repository linting and formatting.

    line 152
  12. Distinctive:

    Always use Bun for package management and script execution.

    line 260
  13. Very specific:

    Prefer standard node: imports for built-in modules.

    line 261
  14. Very specific:

    Use bun:test instead of node:test.

    line 262
  15. Distinctive:

    Prefer Bun-native runtime features only when repository portability is not required.

    line 263
  16. Very specific:

    Check Bun compatibility documentation before assuming a Node.js feature is unsupported.

    line 264
  17. Distinctive:

    Prefer workspace commands from the repository root.

    line 265
  18. Distinctive:

    Run validation before committing repository changes.

    line 266
  19. Distinctive:

    Keep workspace dependencies synchronized.

    line 267
  20. Very specific:

    Use workspace:* for internal package dependencies.

    line 268
  21. Distinctive:

    Use Turborepo to execute workspace tasks instead of running packages individually when possible.

    line 269
  22. Distinctive:

    Keep Bun updated across development environments.

    line 289
  23. Very specific:

    Prefer standard node: module specifiers for built-in modules.

    line 290
  24. Very specific:

    Use bun:test for repository tests.

    line 291
  25. Distinctive:

    Prefer documented Bun APIs over undocumented compatibility workarounds.

    line 292
  26. Distinctive:

    Run commands from the repository root unless package-specific behavior is required.

    line 294
  27. Distinctive:

    Use Turborepo to orchestrate workspace tasks.

    line 296
  28. Distinctive:

    Keep internal packages versioned through the workspace.

    line 297
  29. Very specific:

    Prefer reproducible installations with bun install --frozen-lockfile in CI.

    line 298
  30. Very specific:

    Use catalog: for shared external dependencies.

    line 299
  31. Very specific:

    Use named catalogs to group related tooling (for example: biome, commit, markdown).

    line 300
  32. Distinctive:

    Update dependency versions in the root catalog instead of individual workspace packages.

    line 301
  33. Very specific:

    Use workspace:* only for internal packages.

    line 302

“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Bun

This skill explains how Bun is used throughout the hr-skills monorepo. It covers workspace management, development workflows, validation commands, testing, and repository conventions.

The repository standardizes on Bun for all package management and script execution. Turborepo orchestrates tasks across workspace packages.

Supported tasks

  • Explain how Bun is used within this repository
  • Install and manage workspace dependencies
  • Run repository scripts using Bun
  • Validate HR skills and repository metadata
  • Synchronize generated repository artifacts
  • Build workspace packages
  • Run tests and TypeScript type checking
  • Troubleshoot Bun workspace issues
  • Recommend Bun workflows for local development and CI
  • Explain Bun compatibility with Node.js
  • Recommend Bun-native APIs when appropriate
  • Explain when to use Bun-specific features versus Node.js APIs

Repository usage

This repository uses Bun for:

  • package management
  • workspace dependency resolution
  • script execution
  • TypeScript execution
  • test execution

Package managers such as npm, pnpm, and Yarn are not supported.

Dependency catalogs

This repository centralizes shared dependency versions using Bun catalogs.

Catalogs ensure that common dependencies are defined once in the root package.json and reused consistently across every workspace package.

Workspace packages should reference shared dependencies using the catalog: protocol instead of repeating version numbers.

Use the default catalog.

{
  "dependencies": {
    "typescript": "catalog:"
  }
}

Use a named catalog.

{
  "devDependencies": {
    "@biomejs/biome": "catalog:biome",
    "@commitlint/cli": "catalog:commit"
  }
}

Benefits:

  • keeps dependency versions consistent across the repository
  • updates shared dependency versions in one place
  • reduces duplicated version declarations
  • simplifies workspace maintenance

Internal workspace packages should continue using the workspace:* protocol.

Node.js compatibility

When working in this repository:

  • Assume Node.js APIs are supported unless Bun documentation states otherwise.
  • If a package works in Node.js but fails in Bun, treat it as a Bun compatibility issue rather than a repository issue.
  • Prefer standard node: imports for built-in Node.js modules.
  • Prefer Bun-native APIs only when they provide a clear repository benefit.

Workspace packages

The repository currently contains multiple Bun workspace packages.

hr-skills-build

Repository tooling responsible for:

  • validating HR skills
  • synchronizing repository metadata
  • maintaining repository conventions

hr-skills-ref

Reusable library responsible for:

  • parsing SKILL.md
  • loading skills
  • validating metadata
  • generating prompts
  • exposing reusable APIs for other packages

Common commands

Install dependencies.

bun install

Run validation.

bun run validate

Synchronize generated repository artifacts.

bun run sync

Build every workspace package.

bun run build

Run all test suites.

bun run test

Run TypeScript type checking.

bun run typecheck

Run repository linting and formatting.

bun run check
bun run lint
bun run format
bun run lint:md
bun run lint:md:fix
bun run lint:links

Analyze unused files and dependencies.

bun run knip

Create a release.

bun run release

Key prompts

Compatibility

  • "Explain Bun compatibility with Node.js."
  • "Does this Node.js package work with Bun?"
  • "Explain whether this Node.js API is supported."
  • "Recommend the Bun-native alternative."

Repository workflows

  • "Explain how Bun is used in this repository."
  • "List the common Bun commands used during development."
  • "Describe the repository workspace structure."
  • "Explain how Turborepo and Bun work together."

Validation

  • "Run the repository validation workflow."
  • "Explain what bun run validate does."
  • "Explain what bun run sync does."
  • "Recommend the correct validation order before opening a pull request."

Development

  • "Build every workspace package."
  • "Run all tests using Bun."
  • "Run TypeScript type checking."
  • "Explain how to troubleshoot Bun workspace issues."

CI

  • "Generate a Bun-based CI workflow."
  • "Recommend the fastest validation pipeline."
  • "Explain how to use Turborepo caching."
  • "Generate GitHub Actions steps for Bun."

CI recommendations

A typical validation workflow is:

bun ci
bun run typecheck
bun run validate
bun run test
bun run build

This order detects type, validation, and test failures before building distributable artifacts.

Examples

Install dependencies.

bun install

Validate the repository.

bun run validate

Synchronize repository metadata.

bun run sync

Build every package.

bun run build

Run all tests.

bun run test

Tips

  • Always use Bun for package management and script execution.
  • Prefer standard node: imports for built-in modules.
  • Use bun:test instead of node:test.
  • Prefer Bun-native runtime features only when repository portability is not required.
  • Check Bun compatibility documentation before assuming a Node.js feature is unsupported.
  • Prefer workspace commands from the repository root.
  • Run validation before committing repository changes.
  • Keep workspace dependencies synchronized.
  • Use workspace:* for internal package dependencies.
  • Use Turborepo to execute workspace tasks instead of running packages individually when possible.

Common issues

  • Using npm, pnpm, or Yarn instead of Bun.
  • Ignoring workspace dependency relationships.
  • Assuming unsupported behavior without checking Bun compatibility.
  • Using node:test instead of bun:test.
  • Depending on Node.js APIs that Bun documents as partially implemented.
  • Skipping repository validation before committing.
  • Forgetting to synchronize generated repository artifacts.
  • Running package scripts from the wrong workspace.
  • Missing bun install after dependency changes.
  • Hardcoding dependency versions that should come from a shared catalog.
  • Using explicit semver instead of catalog: for repository-standard dependencies.
  • Updating versions in workspace packages instead of the root catalog.
  • Using catalog: for internal workspace packages instead of workspace:*.

Best practices

  • Keep Bun updated across development environments.
  • Prefer standard node: module specifiers for built-in modules.
  • Use bun:test for repository tests.
  • Prefer documented Bun APIs over undocumented compatibility workarounds.
  • Mention Bun compatibility limitations only when they are relevant to the task.
  • Run commands from the repository root unless package-specific behavior is required.
  • Validate changes before opening a pull request.
  • Use Turborepo to orchestrate workspace tasks.
  • Keep internal packages versioned through the workspace.
  • Prefer reproducible installations with bun install --frozen-lockfile in CI.
  • Use catalog: for shared external dependencies.
  • Use named catalogs to group related tooling (for example: biome, commit, markdown).
  • Update dependency versions in the root catalog instead of individual workspace packages.
  • Use workspace:* only for internal packages.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.