gjalla-code-review
Review Code Changes Before Merge
Code changes can hide correctness, security, and maintainability issues before merge. This skill reviews diffs from relevant perspectives and returns prioritized, location-specific fixes.
Установить с помощью моего Агента
Скопируйте этот запрос в своего Агента. Он содержит каноническую страницу Skill и манифест.
Review the Skillstore skill "gjalla-code-review" from https://skillstore.io/skills/gjalla-gjalla-code-review.md and its manifest at https://skillstore.io/api/skills/gjalla-gjalla-code-review/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Ваш Агент по-прежнему должен показать план и запросить все подтверждения, требуемые политикой безопасности.
Ресурсы для AI-агентов
Используйте эти ссылки, когда AI-агенту, crawler или script нужен чистый контекст вместо полной страницы.
Протестировать
Использование «gjalla-code-review». Review a change that adds payment retry behavior after request timeouts.
Ожидаемый результат:
Blocking — [changed file]:[line]. The retry path can submit a payment twice after a timeout. Add idempotency and test timeout recovery. Not verified: integration tests.
Использование «gjalla-code-review». Review a pull request that introduces a shared cache for user preferences.
Ожидаемый результат:
Should fix — [changed file]:[line]. The cache key does not include the user identifier, so preferences can cross accounts. Scope keys per user and add isolation tests.
Использование «gjalla-code-review». Review a focused documentation-only naming correction.
Ожидаемый результат:
No Blocking or Should fix findings. The updated term is consistent throughout the provided diff. Not verified: references outside the supplied files.
Аудит безопасности
БезопасноThe only static finding is a false positive: line 23 uses Markdown backticks to format `file:line` in prose. SKILL.md contains review guidance only, with no executable code, command invocation, or semantic threat identified.
Факторы риска
⚙️ Внешние команды (1)
Поделиться и цитировать этот отчет
Делитесь версионным отчетом об оценке, нейтральным значком, встраиваемой карточкой и цитатами. Skillstore публикует доказательства, не решая, безопасен ли этот Skill.
Копировать ссылку на отчёт
https://skillstore.io/skills/gjalla-gjalla-code-review/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportЗначок Markdown
[](https://skillstore.io/skills/gjalla-gjalla-code-review?utm_source=security_passport_badge)Значок HTML
<a href="https://skillstore.io/skills/gjalla-gjalla-code-review?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/gjalla-gjalla-code-review/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Встраиваемая карточка
<iframe src="https://skillstore.io/embed/skills/gjalla-gjalla-code-review.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Академические ссылки (APA · BibTeX · CFF)
Цитата APA
gjalla. (2026). gjalla-code-review security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/gjalla-gjalla-code-review/audits/1Цитата BibTeX
@techreport{gjalla-gjalla-gjalla-code-review-2026,
author = {gjalla},
title = {gjalla-code-review security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/gjalla-gjalla-code-review/audits/1},
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: "gjalla-code-review security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "gjalla"
date-released: "2026-08-11"
url: "https://skillstore.io/skills/gjalla-gjalla-code-review/audits/1"
identifiers:
- type: other
value: "skillstore:gjalla-gjalla-code-review:audit:1"
description: "Skillstore immutable audit report identifier"
Оценка Skillstore
Почему такая оценка Достоверность доказательств: СреднийЧто вы можете построить
Review Before Opening a Pull Request
Find blocking defects and missing tests before requesting review from teammates.
Assess Merge Readiness
Prioritize actionable findings and decide whether a pull request is ready to merge.
Evaluate Product and Quality Impact
Examine user impact, acceptance criteria, failure modes, and maintainability across a proposed change.
Попробуйте эти промпты
Review this diff for merge readiness. Group findings as Blocking, Should fix, or Nit. Include location, problem, fix, and verification limits.
Review this pull request against its description and acceptance criteria. Focus on correctness, edge cases, tests, and maintainability. Prioritize actionable findings with locations.
Review this change from engineering, product, quality, and security perspectives where relevant. Identify second-order effects and missing handling. Explain merge risk and fixes.
Perform an adversarial ship-readiness review of this diff and linked specification. Trace data access, failure modes, compatibility, and user impact. Report only defensible findings.
Лучшие практики
- Provide the full diff, change intent, acceptance criteria, and relevant specifications.
- Include test results and known constraints so findings can distinguish verified behavior from assumptions.
- Resolve Blocking findings first, then evaluate Should fix items within the release context.
Избегать
- Do not request approval from a partial diff that omits related changes.
- Do not treat automated review as a substitute for tests or accountable human review.
- Do not dismiss findings without checking the cited location, impact, and suggested fix.