Skills common-pitfalls

📦

common-pitfalls

Name: common-pitfalls
Author: BarisSozen

Content revision r1 Safe ⚙️ External commands

Review Common Development Pitfalls

Development teams miss recurring framework and security mistakes during busy reviews. This skill routes code changes to targeted pitfall checks and summarizes review concerns.

Supports: Claude Codex Code(CC)

🥉 78 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "common-pitfalls" from https://skillstore.io/skills/barissozen-common-pitfalls.md and its manifest at https://skillstore.io/api/skills/barissozen-common-pitfalls/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/barissozen-common-pitfalls.md Signed manifest GET /api/skills/barissozen-common-pitfalls/manifest Signed lockfile GET /api/skills/barissozen-common-pitfalls/lockfile

Test it

Using "common-pitfalls". A pull request changes React components, API routes, and database schema files.

Expected outcome:

The review flags React loading states, Express status code handling, and Drizzle type export checks. It groups each concern by affected area.

Using "common-pitfalls". A debugging session includes blockchain RPC failures and WebSocket reconnect issues.

Expected outcome:

The report focuses on RPC error handling, gas estimation, transaction simulation, heartbeat checks, and reconnection behavior.

Using "common-pitfalls". A reviewer asks for security-sensitive pitfall checks before merge.

Expected outcome:

The checklist highlights secrets in logs, session key expiry, stored credential encryption, audit logging, and rate limiting.

Security Audit

Safe

v8 • 7/6/2026 Open versioned report

All nine static findings are false positives caused by Markdown inline code spans in SKILL.md. The skill contains review orchestration guidance and checklist text, with no evidence of shell execution, prompt injection, data exfiltration, or unsafe commands.

Files scanned

Lines analyzed

Review items

False positives ignored

Risk Factors

⚙️ External commands (9)

SKILL.md:25 SKILL.md:26 SKILL.md:27 SKILL.md:28 SKILL.md:29 SKILL.md:30 SKILL.md:31 SKILL.md:66 SKILL.md:79

No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/barissozen-common-pitfalls/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/barissozen-common-pitfalls/security.svg)](https://skillstore.io/skills/barissozen-common-pitfalls?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/barissozen-common-pitfalls?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/barissozen-common-pitfalls/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/barissozen-common-pitfalls.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

BarisSozen. (2026). common-pitfalls security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/barissozen-common-pitfalls/audits/8

BibTeX citation

@techreport{barissozen-barissozen-common-pitfalls-2026,
  author = {BarisSozen},
  title = {common-pitfalls security audit report (audit version 8)},
  institution = {Skillstore},
  year = {2026},
  number = {8},
  url = {https://skillstore.io/skills/barissozen-common-pitfalls/audits/8},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "common-pitfalls security audit report (audit version 8)"
version: "unspecified"
type: report
authors:
  - name: "BarisSozen"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/barissozen-common-pitfalls/audits/8"
identifiers:
  - type: other
    value: "skillstore:barissozen-common-pitfalls:audit:8"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Pre-commit quality review

Check changed frontend, backend, data, and security files before committing work.

Pull request triage

Route a pull request to relevant pitfall checks and collect concerns for reviewers.

Production issue investigation

Review suspect code areas for known pitfalls after an incident or bug report.

Try These Prompts

Run a basic pitfall review

Review these changed files for common development pitfalls. Identify the matching categories and summarize the highest priority concerns.

Check a pull request

Use the common pitfalls workflow on this pull request. Group findings by TanStack Query, Drizzle, Express, React, WebSocket, blockchain, and security when relevant.

Investigate a production bug

Analyze this bug-related code for recurring pitfalls. Focus on lifecycle state, database types, API responses, RPC failures, logging, and secrets exposure.

Coordinate a full-stack audit

Map this change set to all relevant pitfall sub-skills, combine their findings, rank risks by impact, and recommend concrete fixes for each affected area.

Best Practices

Use the skill after collecting the changed files and the purpose of the change.
Follow up with the relevant specialized pitfall skill when a category matches.
Convert each finding into a concrete code change, test, or reviewer question.

Avoid

Do not treat the combined checklist as proof that the code is secure.
Do not run every sub-skill when the change clearly touches only one category.
Do not ignore project-specific conventions when applying generic pitfall guidance.

Frequently Asked Questions

What does this skill review?

It reviews common pitfalls across query handling, database schemas, APIs, React components, WebSockets, blockchain calls, and security-sensitive code.

Does it execute commands?

No. The skill is documentation and workflow guidance for review. It does not include scripts or shell commands.

Can it replace framework-specific review?

No. It routes work to relevant sub-skills and checklists. Detailed review still depends on the focused guidance.

When should I use it?

Use it during code review, before commits, when debugging incidents, or when reviewing unfamiliar code patterns.

Which tools can use it?

The report marks support for Claude, Codex, and Claude Code.

What output should I expect?

Expect grouped findings, affected categories, and checklist items that point reviewers toward likely fixes.

Developer Details

Author

BarisSozen

License

MIT

Skillstore revision

Version notice

The author did not declare a version.

Repository

https://github.com/BarisSozen/claude/tree/main/.claude/skills/common-pitfalls

Ref

c4231f0153ccd2a2ed62274c5a372bf8f2386d3f

Maintenance freshness

7/18/2026

Usage

6 downloads · 253 views

File structure

📄 SKILL.md