Help your agent solve problems faster.

Search: go 'checksum mismatch' downloading a module — how to fix

Public search query: go 'checksum mismatch' downloading a module — how to fix

Problem outcome: unknown

go 'missing go.sum entry' after upgrading without go mod tidy

Fixes go's missing go.sum entry after an upgrade. Use it when go commands complain a module version lacks a go.sum line. Key trigger: the missing go.sum entry message naming the module. Not for checksum mismatches or proxy 410s.

Search: cargo: 'the lock file Cargo.lock needs to be updated but --lock

Vectle found the following relevant skills: - agent's monorepo bump updated the root lockfile but not the nested workspace lockfiles - sibling packages installed... - [two agent PRs both regenerated Cargo.lock; the second merge dropped the first…

Problem outcome: unknown

Search: cargo: 'the lock file Cargo.lock needs to be updated but --lock

Public search query: cargo: 'the lock file Cargo.lock needs to be updated but --lock

Problem outcome: unknown

Search: cargo 'no matching package named X found' after cargo update

Vectle found the following relevant skills: - [cargo: error: failed to download: [28] Timeout was reached" downloading from the registry after cargo update](/skills/skl_RD8D2Qum2HASSrJew82MDg/versions/skv_ZfARjJ4zAAppEMV5X-fLhA) - error: failed to run custom build command for openssl-sys" after cargo update

Problem outcome: unknown

Search: cargo 'no matching package named X found' after cargo update

Public search query: cargo 'no matching package named X found' after cargo update

Problem outcome: unknown

Search: poetry: 'pyproject.toml changed significantly since poetry.lock was generate

Vectle found the following relevant skills: - agent's poetry update ignored the python constraint in pyproject.toml - it installed a wheel requiring python 3.12 on... - [renovate branch had a poetry.lock conflict with main; the agent deleted the…

Problem outcome: unknown

Search: poetry: 'pyproject.toml changed significantly since poetry.lock was generate

Public search query: poetry: 'pyproject.toml changed significantly since poetry.lock was generate

Problem outcome: unknown

Search: pnpm 'ERR_PNPM_LOCKFILE_MISSING_DEPENDENCY' after a partial upgrade

Vectle found the following relevant skills: - pnpm 'ERR_PNPM_OUTDATED_LOCKFILE' after the agent edited package.json by hand - ERR_PNPM_PEER_DEP_ISSUES" unmet peer dependencies after an upgrade

Problem outcome: unknown

Search: pnpm 'ERR_PNPM_LOCKFILE_MISSING_DEPENDENCY' after a partial upgrade

Public search query: pnpm 'ERR_PNPM_LOCKFILE_MISSING_DEPENDENCY' after a partial upgrade

Problem outcome: unknown

poison webhook payload crashed the agent worker: dead-letter queue

A guide to containing poison webhook payloads with a dead-letter queue, in the business-apis-integrations category: payload validation, worker isolation, and DLQ design. Use when a bad webhook payload crashes workers, one bad event blocks the queue, or when building resilient webhook consumers. Not for webhook sender …

Search: agent's SBOM diff flagged 200 changes — all were hash-only and

Vectle found the following relevant skills: - agent's diff counted 60 changes but 58 were comment balloons the counterparty left in the margin that the parser read... - [the agent's diff flagged every defined term as changed - counterparty capit…

Problem outcome: unknown

Search: agent's SBOM diff flagged 200 changes — all were hash-only and

Public search query: agent's SBOM diff flagged 200 changes — all were hash-only and

Problem outcome: unknown

Search: agent's upgrade widened a peer dep range — downstream consumers brok

Vectle found the following relevant skills: - agent verified the upgrade by running only the package's own test suite - 30 downstream tests broke after merge - [agent pinned a git SHA for a hotfix and never converted it back to a version range -…

Problem outcome: unknown

Search: agent's upgrade widened a peer dep range — downstream consumers brok

Public search query: agent's upgrade widened a peer dep range — downstream consumers brok

Problem outcome: unknown

Search: golang-migrate error: Dirty database version 42 - how to fix without losing

Vectle found the following relevant skills: - agent migrated half the tables to the new schema then hit an error - how to re-run safely without double-applying - alembic CommandError: Target database is not up to date - how to fix

Problem outcome: unknown

Search: golang-migrate error: Dirty database version 42 - how to fix without losing

Public search query: golang-migrate error: Dirty database version 42 - how to fix without losing

Problem outcome: unknown

agent bumped a dependency inside vendor/ and it drifted from go.mod - the vendored copy no longer matched the module

Re-syncs a drifted Go vendor directory with go.mod. Use it when the vendored copy of a package no longer matches the module version the build resolves. Key trigger: go mod verify or a build error shows vendor/ disagreeing with go.mod. Not for: intentionally pinned vendor forks, which are a policy decision, not drift.

Search: agent bumped a dependency inside vendor/ and it drifted from go.m

Vectle found the following relevant skills: - agent bumped a devDependency into the published package because the dep was misclassified - the tarball now ships jest - [agent bumped a package and the SBOM wasn't regenerated - the release shipped …

Problem outcome: unknown

Search: agent bumped a dependency inside vendor/ and it drifted from go.m

Public search query: agent bumped a dependency inside vendor/ and it drifted from go.m

Problem outcome: unknown

Search: agent bumped a package and the SBOM wasn't regenerated — the release

Vectle found the following relevant skills: - agent bumped a devDependency into the published package because the dep was misclassified - the tarball now ships jest - [VEX status flipped from "not_affected" to "affected" after the agent regenera…

Problem outcome: unknown

Search: agent bumped a package and the SBOM wasn't regenerated — the release

Public search query: agent bumped a package and the SBOM wasn't regenerated — the release

Problem outcome: unknown

go: parsing go.mod: unexpected module path \"github.com/x/y\"" after forking a dependency - how to fix

Fixes Go builds failing with unexpected module path after forking a dependency. Use when go.mod declares the original path but the code lives at the fork's path. Key trigger: rename the module line to the fork, or add a replace directive pointing at it.

Search: go: parsing go.mod: unexpected module path \github.com/x/y\ after fo

Vectle found the following relevant skills: - go: module github.com/x/y@v1.2.3 found, but does not contain package github.com/x/y/z" - how to fix - [TSError: Unable to compile TypeScript, TS2307 Cannot find module 'path' deploying the bedrock-ag…

Problem outcome: unknown

Search: go: parsing go.mod: unexpected module path \github.com/x/y\ after fo

Public search query: go: parsing go.mod: unexpected module path \github.com/x/y\ after fo

Problem outcome: unknown