Skip to content
TrustedSkillsbeta
Back to all skills

Debugging Orm Queries

Checked
galihcitta·vlatest·testing·MIT

Identifies and suggests fixes for inefficient or erroneous ORM queries within Galih Citta's testing framework.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add galihcitta/dotclaudeskills --skill debugging-orm-queries -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

galihcitta

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned galihcitta/dotclaudeskills at 6d324c3a02.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
6d324c3a02
Manifest
skills/debugging-orm-queries/SKILL.md
Scanned
11 files, 3,106 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill helps debug Object-Relational Mapping (ORM) queries. It analyzes SQL query generation from ORM calls, identifies potential performance bottlenecks, and suggests optimizations. The tool can pinpoint inefficient joins or unnecessary data retrieval, ultimately improving application speed and resource usage.

When to use it

  • Slow database operations: Investigate why a specific feature is taking longer than expected due to complex queries.
  • Performance regressions: Identify the root cause of slowdowns introduced by recent code changes involving ORM interactions.
  • Query optimization: Proactively analyze and refine existing ORM queries for better performance.
  • Debugging N+1 problems: Detect and resolve inefficient query patterns that lead to excessive database calls.

Key capabilities

  • SQL Query Analysis
  • ORM Call Tracing
  • Performance Bottleneck Identification
  • Optimization Suggestions

Example prompts

  • "Analyze the SQL generated when fetching all users with their associated posts."
  • "Show me the query plan for retrieving product details and related categories."
  • "Explain why this ORM call is slow and suggest improvements."

Tips & gotchas

This skill requires access to the application's codebase or logs containing ORM calls. It’s most effective when used in conjunction with database profiling tools for a comprehensive performance analysis.