Results for “package-registry”

Install, discover, and wire reusable blocks and components into HyperFrames compositions using the CLI.

Manages Python package publishing, versioning, and distribution builds on PyPI, including dependency resolution, index configuration, and package health analysis.

Push Packer build metadata to HCP Packer registry for tracking and managing image lifecycle. Use when integrating Packer builds with HCP Packer for version control and governance.

Python package reorganization with pyproject.toml inside package directory

Broad risk assessment — key-person, technical, regulatory, competitive, financial, and execution risks beyond product/market

Integrate an exact reviewed PR under repository policy, choose truthful history semantics, and verify cleanup

Flag misspelled, brandjacked, and typosquatted package names across npm, PyPI, and crates.io before installation using edit-distance, keyboard-proximity, and known-target corpus matching with typomania, OSSGadget, and pypi-scan.

Prepare bid packages with specifications and requirements. TRIGGERS - Use when user needs help with bid-package related tasks.

Use this when a Python repository needs package-level planning, import boundaries, module naming, reusable library extraction, or distribution-friendly structure.

Safely upsert, inspect, review, or explicitly merge the pull request for an issue-backed work branch

Review local branch changes for bugs, security vulnerabilities, and code quality issues using a structured checklist-driven process.

Use this when reviewing how a codebase organizes configuration files, env vars, runtime options, feature flags, and per-environment settings. Trigger on requests to clean up or validate config structure.

Debt that exists only in engineers' heads cannot be prioritised, funded, or

Create distributable Python packages with proper project structure, setup.py/pyproject.toml, and publishing to PyPI. Use when packaging Python libraries, creating CLI tools, or distributing Python code.

Imported skill package from vercel

Reviews lockfiles, installers, provenance, CI permissions, dependency confusion, artifacts, registries, and publishing.

REJESTR KONFIGURACJI (ConfigReg) platformy Soneta (enova365, Triva) od strony kodu C#: drzewo węzłów, providery `IConfigRegProvider` (Root/Module/Table/Row/SubRow/SubTable/Storage/Addins), atrybut `[ConfigReg(Hide/Ignore/Include/ChildrenType)]`, format `*.reg.json`, potok Loader → Differ/Merger → SessionUpdater. Używaj ZAWSZE gdy użytkownik: (1) pyta o rejestr konfiguracji, ConfigReg, `Soneta.Config.Reg`, tabelę `ConfigRegistry` lub menu „Zarządzanie konfiguracją"; (2) chce włączyć/wyłączyć tabelę, kolumnę lub węzeł z rejestru (`Ignore`, `Hide`, `Include`, `ChildrenType`); (3) pisze provider rejestru, obsługę zapisu (`SaveChild`, `delayed`), porównywanie (`ConfigRegDiffer`), scalanie (`ConfigRegMerger`), serializację (`RegConfigJsonConverter`); (4) buduje lub debuguje `*.reg.json` — sigile `$strict`, `$v`, `#klucz`, `@atrybut`, `$blob`, ścieżki `Business/FeatureDefs/Name=CECHA`; (5) przenosi ustawienia między bazami przez rejestr. Import/eksport przez XML (`dbinit.xml`) to INNY mechanizm → /soneta-config.

Use this when a Python service, package, or repository needs a maintainable internal structure for modules, domain logic, adapters, config, entrypoints, and tests. Trigger on requests about project layout and internal organization for Python systems.

Records common pitfalls and assumptions for Python module execution and GitHub Actions sparse checkout setups.

Archive multiple completed changes at once. Use when archiving several parallel changes.

Privacy Policy Generator

Publish to npm, create README, set up repo, and log the shipment

Align TypeScript module resolution, package exports, and declaration emit so that consumers can import the published artifact under every supported runtime and bundler.

Routes Salesforce Apex and SOQL questions to the right skill package from a registry of 158, covering triggers, governor limits, async processing, callouts, security, and tests.

Package and publish a skill to the skills.sh community registry, a public GitHub repo, or both. Load when the user asks to publish a skill, share a skill publicly, submit a skill to the registry, release a skill, or when universal-skill-creator offers publishing as a final step after creation. Also triggers on "push this skill to skills.sh", "make this skill public", "share this skill", or "contribute this skill to the community". Validates quality before publishing, packages correctly (zip for multi-file, .md for atomic), writes a README if missing, and publishes via npx skills CLI.