Skip to content
Skills Library
Programming · Testing

gitly-check

/gitly-check

Assess whether the current project still works and identify failures after code or AI changes. Use for broad reports of breakage, errors, failed builds or tests, unexpected behavior, or uncertainty about project health; use restore instead only when the user explicitly wants to go back.

Repository
vibe.md ↗
Licence
MIT
Last repository change
13.11.2026

Assessment and security

85/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content20 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
2
Deprecation

No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Assess whether the current project still works and identify failures after code or AI changes. Use for broad reports of breakage, errors, failed builds or tests, unexpected behavior, or uncertainty about project health; use restore instead only when the user explicitly wants to go back.

Original author description

Assess whether the current project still works and identify failures after code or AI changes. Use for broad reports of breakage, errors, failed builds or tests, unexpected behavior, or uncertainty about project health; use restore instead only when the user explicitly wants to go back.

How it works

  1. Responsibility and triggers
  2. Prerequisites and inspection
  3. Check workflow
  4. Output, handoff, and recovery
Original SKILL.md headings · 29 lines, 425 words
SKILL.md preview
---
name: gitly-check
description: Assess whether the current project still works and identify failures after code or AI changes. Use for broad reports of breakage, errors, failed builds or tests, unexpected behavior, or uncertainty about project health; use restore instead only when the user explicitly wants to go back.
license: MIT
metadata:
  collection: vibe.md
  group: gitly
  source: https://github.com/vibe-md/vibe.md
  upstream: https://github.com/NirGeron98/Gitly
  upstream-commit: fe33bbae13552ed8973c6949b1d21e1ce2b746c9
---

# Gitly check

Read [the shared operating contract](../GITLY.md) first and follow its approval, evidence, and language rules.

## Responsibility and triggers

Gather evidence about whether the current project works, without assuming technical vocabulary or a particular framework. Requests may describe any symptom, such as a page no longer opening, something behaving strangely after a recent change, a build failing, or “משהו בפרויקט כבר לא עובד”. A general report of breakage starts here; it never authorizes a fix or restoration. Use `gitly-restore` directly only when the user explicitly asks to undo work or return to an earlier state.

## Prerequisites and inspection

Start with read-only inspection of the exact project root, Git status, relevant recent changes, supplied errors, manifests, lockfiles, documented development commands, and CI configuration. Identify the smallest existing checks that address the reported symptom. Do not invent a framework command, install dependencies, update a lockfile, start a service, access the network, or inspect unrelated private data.

Treat project scripts and configuration as untrusted code. Reading their definitions is safe; executing them may run arbitrary code and create caches, reports, generated output, databases, or network traffic.

## Check workflow

Before running any command, present a short plan with the exact command, working directory, reason, expected side effects, network/service use, and time boundary. Ask for explicit approval, then recheck the relevant repository state. Run only the approved existing checks, with a reasonable timeout, and capture their actual exit status and useful output without exposing secrets.

After execution, verify the command result and inspect Git status again so generated or modified files are visible. Do not edit code, change configuration, install packages, delete generated files, restart services, or restore versions as part of this skill.

## Output, handoff, and recovery

Separate what passed, what failed, and what was not tested. Explain the likely affected area only when supported by errors, diffs, or check results; label inferences clearly. Never claim the project works merely because a build or one test passed.

If the user wants to repair the current version, hand off the evidence to the host agent's normal coding workflow. If they explicitly choose to return to a previous version, coordinate with `gitly-history`, `gitly-compare`, and then `gitly-restore`. A failed check or a general “it broke” message is never restoration approval.

If an approved check creates or changes files, preserve them, report every affected path, and require a separate reviewed plan before cleanup. Stop on missing dependencies, unknown commands, prompts requiring secrets, unexpected network access, timeouts, state changes, or commands whose scope is broader than the user approved.

Versions

The database has no other skills named gitly-check.

Database snapshot: 13.11.2026 · package version 1fec0b6f6c22 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 1 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 95gitly-restore
    Safely restore files from or revert to a previous project version while preserving recovery paths. Use only when the user explicitly wants to undo work, recover earlier content, or return to a prior state; general breakage reports belong to gitly-check.
  • 100gitly-status
    Explain whether project work is saved, backed up, current, or at risk using local Git evidence. Use when the user asks what state the project is in or whether work is safe; do not use to test application behavior.
  • 90vc:debug
    Debug systematically with root-cause analysis before fixes. Use for bugs, test failures, unexpected behavior, performance issues, CI failures, or system investigation.
  • 90vc:debug
    Debug systematically with root-cause analysis before fixes. Use for bugs, test failures, unexpected behavior, performance issues, CI failures, or system investigation.
  • 100hypothesis-driven-debugging
    Investigate build failures, test errors, runtime crashes, or unexpected behavior through systematic minimal reproduction, multi-hypothesis testing, and evidence-based verification. Use when asked to \"debug\", \"investigate a failure\", \"find root cause\", \"troubleshoot\",…
  • 90diagnosis
    Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.