Skip to content
TrustedSkillsbeta
Back to all skills

Check

Listed
continuedev·vlatest·backend

This "Check" skill verifies information against a specified source, ensuring accuracy and reducing misinformation risks for reliable outputs.

Repository

Install on your platform

This skill no longer installs under the name check. continuedev/skills is deleted or private, so it cannot be installed from.

We check each listing against its upstream repository with the rules the skills CLI uses, last on 2026-10-23. We don't show a command we know will fail.

Repository install instructions

What we know about this skill

Publisher

continuedev

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.

Nobody has reviewed this code. TrustedSkills indexes and links skills; it does not audit, run or scan them. A skill runs with whatever access you give your agent — read the source before you install it.

Automated safety checks

scanned

We could not read this skill's source, so none of the checks below were run.

Not scanned. repository not found or private Source recorded as continuedev/skills.
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, named "Check," automates verification of code changes against predefined checks written in Markdown files. It gathers context by creating temporary files containing git diffs and commit logs, then launches background agents to review these changes based on the instructions within those check files. The skill aggregates results and presents a summary table to the user, highlighting any failures for triage.

When to use it

  • To automatically enforce code conventions during development.
  • To identify potential security vulnerabilities in code changes.
  • To ensure test quality before merging code.
  • When working on projects with established coding standards and automated checks.
  • For continuous integration workflows where consistent code review is needed.

Key capabilities

  • Diff Generation: Creates temporary files containing git diffs (limited to 3000 lines) and commit logs.
  • Check Discovery: Identifies available check files from the .continue/checks/*.md directory.
  • Parallel Execution: Runs checks concurrently using background agents.
  • Structured Reporting: Provides a summary table of check results (PASS or FAIL).
  • Targeted Feedback: Presents individual findings for failed checks via AskUserQuestion.

Example prompts

  • "Run all available checks."
  • "Verify the latest changes against the code conventions and security checks."
  • "Check my work for test quality issues."

Tips & gotchas

  • The skill relies on git being installed and configured.
  • Checks are defined in Markdown files located within the .continue/checks/ directory.
  • Large diffs (over 3000 lines) will be truncated, potentially impacting the accuracy of some checks.