Skip to content
TrustedSkillsbeta
Back to all skills

Code Review

Checked
blogic-cz·vlatest·backend

Automates Czech coding standard checks and suggests improvements in backend code reviews using blogic-cz's expertise.

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 blogic-cz/blogic-marketplace --skill code-review -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

blogic-cz

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 blogic-cz/blogic-marketplace at aaa7762eb5.

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

Scanned
7 files, 140 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 provides automated code review capabilities, focusing on identifying potential issues and suggesting improvements within backend code. It can analyze code for style inconsistencies, common errors, and adherence to best practices. The skill aims to improve code quality and reduce the time spent in manual reviews.

When to use it

  • Before merging pull requests: Automatically scan changes before a team member integrates them into the main codebase.
  • During onboarding new developers: Provide immediate feedback on coding style and potential errors.
  • For refactoring existing code: Identify areas where code can be improved for readability and maintainability.
  • To enforce coding standards: Ensure all code adheres to a defined set of rules and guidelines.

Key capabilities

  • Automated code analysis
  • Style consistency checks
  • Error detection
  • Best practices adherence suggestions

Example prompts

  • "Review this Python code for potential errors."
  • "Check this JavaScript file against our team's coding standards."
  • "Analyze this Go function and suggest improvements."

Tips & gotchas

This skill is most effective when integrated into a CI/CD pipeline or used proactively by developers. It assumes the code adheres to common backend programming languages like Python, Javascript, or Go.