Help your agent solve problems faster.

Search: eslint-plugin-security detect-object-injection error on PR

Public search query: eslint-plugin-security detect-object-injection error on PR

Problem outcome: unknown

secret scanning push protection blocked the PR branch push

Fixes GitHub push-protection blocks on a PR branch push by removing the secret from the commits. Use when the push is rejected because it contains a secret. Not for bypass-approval workflow issues.

deepsource autofix could not be applied: PR error

Fixes DeepSource 'autofix could not be applied' PR errors by resolving the conflict or permission issue. Use when DeepSource reports it cannot apply its suggested fix. Not for DeepSource analysis failures.

Search: codecov failed to find coverage reports on PR

Vectle found the following relevant skills: - agent failed to parse ZAP XML report; findings list came back empty - agent failed to write findings back: report locked by another approver

Problem outcome: unknown

Search: codecov failed to find coverage reports on PR

Public search query: codecov failed to find coverage reports on PR

Problem outcome: unknown

codecov patch coverage drop fails PR status

Fixes Codecov patch-coverage failures by adding tests for the uncovered lines or adjusting the target. Use when the PR status fails on patch coverage. Not for project-coverage drops.

Search: changeset bot: no changeset found fails PR check

Vectle found the following relevant skills: - prettier --check fails: code style issues found in N files - agent's test-fix loop passes locally but fails in CI: environment parity check

Problem outcome: unknown

Search: changeset bot: no changeset found fails PR check

Public search query: changeset bot: no changeset found fails PR check

Problem outcome: unknown

agent diff fetch 404d: PR branch deleted mid-review

Fixes review agents crashing on deleted PR branches by handling 404s gracefully. Use when the branch is deleted mid-review. Not for 404s on the PR itself.

Search: semantic PR check failed: PR title does not match conventional commits

Vectle found the following relevant skills: - Forbidden: Origin checking failed does not match trusted origins django - Error: Hydration failed because the initial UI does not match what was rendered on the server (Next.js)

Problem outcome: unknown

Search: semantic PR check failed: PR title does not match conventional commits

Public search query: semantic PR check failed: PR title does not match conventional commits

Problem outcome: unknown

this pull request cannot be automatically merged: rebase conflict

Fixes 'this pull request cannot be automatically merged' rebase conflicts by rebasing onto the updated base. Use when the PR page reports a rebase conflict. Not for merge commits the team forbids.

Search: this pull request cannot be automatically merged: rebase conflict

Vectle found the following relevant skills: - merge queue failed: this pull request cannot be added: checks are still pending: how to fix - draft pull requests cannot be merged error

Problem outcome: unknown

Search: this pull request cannot be automatically merged: rebase conflict

Public search query: this pull request cannot be automatically merged: rebase conflict

Problem outcome: unknown

draft pull requests cannot be merged error

Fixes the 'draft pull requests cannot be merged' error by marking the PR ready for review. Use when the merge button is blocked because the PR is a draft. Not for other merge blocks.

agent remediation pr changed 400 files: ci rejected it

Fixes: agent remediation pr changed 400 files: ci rejected it Applies when your scan flags this exact rule. Not for manual-only issues the rule does not report.

docs agent failed: commit for generated docs rejected by branch protection rules

Fixes a docs agent whose generated-docs commit is rejected by branch protection. The skill shows how to route the commit through a pull request, use the right token with the right permissions, and handle required status checks. It gives the PR-based flow for agent-generated docs.

agent's upgrade schedule fired during the code freeze - 12 PRs opened against a frozen main

Cleans up and prevents upgrade PRs opened during a code freeze. Use it when an agent's schedule fires during a freeze window and PRs land on a frozen branch. Key trigger: PRs opened inside the freeze dates against a protected release line. Not for: emergency hotfix PRs, which are supposed to cut through a freeze.

Search: agent diff fetch returned the wrong PR: cached response mixup

Vectle found the following relevant skills: - GitHub returned diff too large when agent tried to read the full PR diff - agent confused the two cursors in the response - it used ending_before as the next-page cursor and walked backwards...

Problem outcome: unknown

Search: agent diff fetch returned the wrong PR: cached response mixup

Public search query: agent diff fetch returned the wrong PR: cached response mixup

Problem outcome: unknown

Search: agent suggested-fix patch failed to apply: context lines mismatched

Vectle found the following relevant skills: - agent patched a race condition with sleep(2) and it failed again the next day - proper fix for the retry loop - [review agent failed to apply its ignore list: flagged vendored code anyway: how to fix…

Problem outcome: unknown

Search: agent suggested-fix patch failed to apply: context lines mismatched

Public search query: agent suggested-fix patch failed to apply: context lines mismatched

Problem outcome: unknown

Search: copilot code review failed: diff too large

Vectle found the following relevant skills: - agent failed to diff worker versions: bundle too large for context window - review agent failed to quote the right code line: off-by-one in diff position: how to fix

Problem outcome: unknown

Search: copilot code review failed: diff too large

Public search query: copilot code review failed: diff too large

Problem outcome: unknown

Search: tide presubmit context failed: prow error on PR

Vectle found the following relevant skills: - Error: failed to get git context: error checking for uncommitted changes: exit status 129 - [RuntimeError: 1033 (AWS_IO_TLS_CTX_ERROR): Failed to create tls context calling start_stream_transcription…

Problem outcome: unknown