@bomb.sh/tools/dist/commands/sync.d.mts

The internal dev, build, and lint CLI for Bombshell projects

import { CommandContext } from "../context.mjs";

//#region src/commands/sync.d.ts
declare function sync(_ctx: CommandContext): Promise<void>;
/**
 * Prefer linking through the project's `node_modules/@bomb.sh/tools` over
 * `import.meta.url`, which resolves to the real path. Under pnpm that is a
 * versioned `node_modules/.pnpm/<hash>/` directory, so links into it dangle
 * once a reinstall changes the hash.
 */
declare function resolveSkillsSource(root: URL, fallback: URL): Promise<URL>;
interface SkillInfo {
  name: string;
  description: string;
}
declare function copySkills(options: {
  source: URL;
  dest: URL;
}): Promise<SkillInfo[]>;
declare function updateAgentsMd(options: {
  root: URL;
  skills: SkillInfo[];
}): Promise<void>;
/**
 * Locate the consuming project's package.json. The project root must come
 * from where the command was invoked, never from this package's physical
 * location: under pnpm's isolated layout, import.meta.url resolves through
 * the node_modules symlink into node_modules/.pnpm/<hash>/, and walking up
 * from there lands in the store, not the user's project. INIT_CWD (set by
 * pnpm/npm to the directory the script was run from) is preferred because
 * package scripts may rewrite cwd. Returns null when no project is found or
 * when invoked inside @bomb.sh/tools itself.
 */
declare function findParentPackage(): Promise<string | null>;
//#endregion
export { copySkills, findParentPackage, resolveSkillsSource, sync, updateAgentsMd };
//# sourceMappingURL=sync.d.mts.map