Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Error Patterns

ASecurity

Known agent error patterns -- debugging reference for tool failures, git errors, CI issues, and common mistakes. Consult when encountering unexpected behavior, tool errors, or CI failures.

5 stars
0 votes
0 copies
0 views
Added 10/4/2026
ai-agentspythongoshelldebugginggitapi

Works with

cliapi

Security Analysis

A92/100
mediumInstalls packages at runtime which could introduce malicious dependencies

Pro scans all 2 files and shows the line behind each finding

Scanned 10/4/2026

$npx -y skills add juan294/cc-rpi --skill error-patterns --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Error Patterns?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Error Patterns
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/juan294-error-patterns-cc-rpi/badge)](https://www.skillsdirectory.com/skills/juan294-error-patterns-cc-rpi)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: "error-patterns"
description: "Known agent error patterns -- debugging reference for tool failures, git errors, CI issues, and common mistakes. Consult when encountering unexpected behavior, tool errors, or CI failures."
---

# Error Patterns -- Top 20

**#1: Lost parallel verification results** --
Use `&&` or aggregate each exit status; bare `;` hides early failures.

**#2: Wrong worktree cwd** --
Bind each call to an observed worktree path or explicit workdir; verify branch.

**#3: Pre-commit hook rejection** --
Run typecheck/lint BEFORE committing. Fix first.

**#8: Tilde in file paths** --
Resolve an absolute path unless that specific file API promises expansion.

**#9: Push rejected (non-fast-forward)** --
Reconcile remote integration history locally, then rerun affected gates.

**#12: Push and forget CI** --
Inspect expected workflows for the authorized pushed commit.

**#13: Skipping TDD** --
Write the failing test FIRST. Red-Green-Refactor.

**#16: Dependencies not installed** --
Run `pnpm install` / `uv sync` before build/test/lint.

**#25: No upstream tracking** --
Working branches remain local; only completed integration may be published.

**#30: PR create before pushing** --
Do not publish a working branch merely to create a PR.

**#33: Pull rebase with dirty tree** --
Commit before `git pull --rebase`.

**#44: Push --tags pushes ALL tags** --
Push only the named authorized release tag: `git push origin v1.0.0`.

**#45: Fabricated filesystem paths** --
Never guess paths. Use Glob/Grep to find files first.

**#48: Commit/push to wrong branch** --
Run `git branch --show-current` before every commit.

**#49: Sub-agent git conflicts** --
Each sub-agent owns different files. Central commit.

**#51: CI explosion from parallel pushes** --
Integrate and verify locally; one authorized integration push may trigger several workflows.

**#56: Merge to main without topology** --
Ask: does merging to main deploy to production?

**#58: Deploy without preview verification** --
Run local runtime and platform preflights; never create Previews.

**#59: Improvised production recovery** --
Roll back immediately. Never deploy to diagnose.

**#62: Supabase migration without local test** --
Test role access with `supabase db reset --local`; remote application is separate.

## Error Domains

- **Shell & Tools:** #1, #2, #8, #16, #17, #22, #24, #36, #45
- **Git:** #3, #6, #9, #11, #15, #18, #25, #33, #44, #48,
  #54, #55
- **GitHub CLI:** #4, #10, #20, #23, #30, #31, #32, #35,
  #39, #52, #53
- **CI & Deployment:** #12, #50, #51, #56, #57, #58, #59, #60
- **Python/macOS:** #21, #26, #29, #37, #38, #40, #41, #42
- **Supabase:** #61, #62
- **Multi-Agent:** #19, #49, #63
- **Process:** #5, #7, #13, #14, #27, #28, #34, #43, #46,
  #47, #64

## References

- `references/error-catalog.md` -- one-line-per-error index of all 64 errors,
  grouped by the same domains above. Read it when the Top 20 above did not
  resolve the issue -- it points you at the right error number before you go
  looking for the full write-up.
- For the full symptom/root-cause/solution detail behind any error number,
  read `patterns/agent-errors.md` in the cc-rpi blueprint repository (not
  part of this project's local files).

Attribution

juan294juan294
View sourceSee grades on GitHubMore from juan294 →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698461 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →