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
- DaleStudy/skillstheir own version, first seen Nov 1, 2026
- hoodini/ai-agents-skillstheir own version, first seen Oct 25, 2026
- G1Joshi/Agent-Skillstheir own version, first seen Oct 13, 2026
- Makiya1202/awesome-codex-computer-usetheir own version, first seen Oct 11, 2026
- bastani-inc/atomictheir own version, first seen Oct 8, 2026
- brianlovin/claude-configtheir own version, first seen Oct 8, 2026
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.
hoodiniSkillanalytics-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
hoodiniSkillaws-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
kelvincushmanSkillgh-commit
Create well-formatted commits with conventional commit format.
Also in 3 projects that use this
LangChainSkilllangchain
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
kelvincushmanSkillprek
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-designSkillgh-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
Other versions15 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 15
- carapace-sh/carapace-bin★ 2ksame name
- bastani-inc/atomic★ 884same name
- flora131/atomic★ 883same name
- brianlovin/claude-config★ 376same name
- hoodini/ai-agents-skills★ 295same name
- mweinbach/agent-coworker★ 157same name
- G1Joshi/Agent-Skills★ 15same name
- belos-street/skill-kit★ 8same name
- nklisch/skills★ 8same name
- DaleStudy/skills★ 4same name
5 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository19 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- biomeSkill
- changesetSkill
- clackSkill
- dry-refactoringSkill
- github-awesome-copilot-git-commitSkill
- hr-root-router-maintainingSkill
- hr-skills-maintainingSkill
- humanizerSkill
- jscpdSkill
- markdownSkill
- pdfSkill
- skill-vetterSkill
- turboSkill
- typescriptSkill
- valibotSkill
- hr-skillsSkill
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
- Distinctive: line 19
Run repository scripts using Bun
- Distinctive: line 23
Run tests and TypeScript type checking
- Distinctive: line 52
Use the default catalog.
- Distinctive: line 62
Use a named catalog.
- Distinctive: line 85
When working in this repository:
- Very specific: line 88
If a package works in Node.js but fails in Bun, treat it as a Bun compatibility issue rather than a repository issue.
- Very specific: line 89
Prefer standard node: imports for built-in Node.js modules.
- Distinctive: line 90
Prefer Bun-native APIs only when they provide a clear repository benefit.
- Distinctive: line 140
Run all test suites.
- Distinctive: line 146
Run TypeScript type checking.
- Distinctive: line 152
Run repository linting and formatting.
- Distinctive: line 260
Always use Bun for package management and script execution.
- Very specific: line 261
Prefer standard node: imports for built-in modules.
- Very specific: line 262
Use bun:test instead of node:test.
- Distinctive: line 263
Prefer Bun-native runtime features only when repository portability is not required.
- Very specific: line 264
Check Bun compatibility documentation before assuming a Node.js feature is unsupported.
- Distinctive: line 265
Prefer workspace commands from the repository root.
- Distinctive: line 266
Run validation before committing repository changes.
- Distinctive: line 267
Keep workspace dependencies synchronized.
- Very specific: line 268
Use workspace:* for internal package dependencies.
- Distinctive: line 269
Use Turborepo to execute workspace tasks instead of running packages individually when possible.
- Distinctive: line 289
Keep Bun updated across development environments.
- Very specific: line 290
Prefer standard node: module specifiers for built-in modules.
- Very specific: line 291
Use bun:test for repository tests.
- Distinctive: line 292
Prefer documented Bun APIs over undocumented compatibility workarounds.
- Distinctive: line 294
Run commands from the repository root unless package-specific behavior is required.
- Distinctive: line 296
Use Turborepo to orchestrate workspace tasks.
- Distinctive: line 297
Keep internal packages versioned through the workspace.
- Very specific: line 298
Prefer reproducible installations with bun install --frozen-lockfile in CI.
- Very specific: line 299
Use catalog: for shared external dependencies.
- Very specific: line 300
Use named catalogs to group related tooling (for example: biome, commit, markdown).
- Distinctive: line 301
Update dependency versions in the root catalog instead of individual workspace packages.
- Very specific: line 302
Use workspace:* only for internal packages.
“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.
Files
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 installRun validation.
bun run validateSynchronize generated repository artifacts.
bun run syncBuild every workspace package.
bun run buildRun all test suites.
bun run testRun TypeScript type checking.
bun run typecheckRun 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:linksAnalyze unused files and dependencies.
bun run knipCreate a release.
bun run releaseKey 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 validatedoes." - "Explain what
bun run syncdoes." - "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 buildThis order detects type, validation, and test failures before building distributable artifacts.
Examples
Install dependencies.
bun installValidate the repository.
bun run validateSynchronize repository metadata.
bun run syncBuild every package.
bun run buildRun all tests.
bun run testTips
- Always use Bun for package management and script execution.
- Prefer standard
node:imports for built-in modules. - Use
bun:testinstead ofnode: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:testinstead ofbun: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 installafter 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 ofworkspace:*.
Best practices
- Keep Bun updated across development environments.
- Prefer standard
node:module specifiers for built-in modules. - Use
bun:testfor 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-lockfilein 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.
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
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.

