📦

safe-refactor

Name: safe-refactor
Author: juliusbrussee

Ревизия содержимого r1 Безопасно

Refactor Code Without Changing Behavior

Structural code changes can introduce subtle regressions and expand scope. This skill defines behavior boundaries and brackets focused refactors with verification.

Поддерживает: Claude Codex Code(CC)

🥉 78 Бронза

Установить с помощью моего Агента

Скопируйте этот запрос в своего Агента. Он содержит каноническую страницу Skill и манифест.

Запрос агента

Review the Skillstore skill "safe-refactor" from https://skillstore.io/skills/juliusbrussee-safe-refactor.md and its manifest at https://skillstore.io/api/skills/juliusbrussee-safe-refactor/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Ваш Агент по-прежнему должен показать план и запросить все подтверждения, требуемые политикой безопасности.

Ресурсы для AI-агентов

Используйте эти ссылки, когда AI-агенту, crawler или script нужен чистый контекст вместо полной страницы.

Markdown-детали GET /skills/juliusbrussee-safe-refactor.md Подписанный manifest GET /api/skills/juliusbrussee-safe-refactor/manifest Подписанный lockfile GET /api/skills/juliusbrussee-safe-refactor/lockfile

Протестировать

Использование «safe-refactor». Move validation from the controller into the domain service without changing API behavior.

Ожидаемый результат:

Boundary: preserve response status, error messages, validation order, and public service signatures.
Sequence: characterize current behavior, move validation, keep the controller adapter, then remove duplication.
Verification: run the same controller and service tests before and after each step.

Использование «safe-refactor». Consolidate duplicate cache invalidation logic used by two modules.

Ожидаемый результат:

Boundary: preserve invalidation timing, key format, failure handling, and call order.
Sequence: introduce one owner, migrate one caller, verify, then migrate the second caller.
Stop condition: both callers use the shared owner and existing behavior remains proven.

Аудит безопасности

Безопасно

v1 • 12.08.2026 Открыть версионный отчет

The only static finding is a false positive caused by a normal refactoring constraint in SKILL.md. No malicious intent, unsafe system access, or prompt injection was found.

Просканировано файлов

Проанализировано строк

Пункты проверки

Ложные срабатывания проигнорированы

Последний завершенный статический и семантический аудит не обнаружил подтвержденных проблем безопасности. Это не доказывает отсутствие побочных эффектов у навыка.

Аудитор:: codex

Поделиться и цитировать этот отчет

Делитесь версионным отчетом об оценке, нейтральным значком, встраиваемой карточкой и цитатами. Skillstore публикует доказательства, не решая, безопасен ли этот Skill.

Открыть версионный отчет

Копировать ссылку на отчёт

https://skillstore.io/skills/juliusbrussee-safe-refactor/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Значок Markdown

[![Skillstore security assessment](https://skillstore.io/badges/skills/juliusbrussee-safe-refactor/security.svg)](https://skillstore.io/skills/juliusbrussee-safe-refactor?utm_source=security_passport_badge)

Значок HTML

<a href="https://skillstore.io/skills/juliusbrussee-safe-refactor?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/juliusbrussee-safe-refactor/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Встраиваемая карточка

<iframe src="https://skillstore.io/embed/skills/juliusbrussee-safe-refactor.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

juliusbrussee. (2026). safe-refactor security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/juliusbrussee-safe-refactor/audits/1

Цитата BibTeX

@techreport{juliusbrussee-juliusbrussee-safe-refactor-2026,
  author = {juliusbrussee},
  title = {safe-refactor security audit report (audit version 1)},
  institution = {Skillstore},
  year = {2026},
  number = {1},
  url = {https://skillstore.io/skills/juliusbrussee-safe-refactor/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: "safe-refactor security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
  - name: "juliusbrussee"
date-released: "2026-08-12"
url: "https://skillstore.io/skills/juliusbrussee-safe-refactor/audits/1"
identifiers:
  - type: other
    value: "skillstore:juliusbrussee-safe-refactor:audit:1"
    description: "Skillstore immutable audit report identifier"

Оценка Skillstore

Почему такая оценка Достоверность доказательств: Средний

Архитектура

Сопровождаемость

Контент

Сообщество

Соответствие спецификации

Что вы можете построить

Extract a Shared Module

Plan a focused extraction while preserving callers, error behavior, and test results.

Move Component Ownership

Transfer one responsibility between packages while keeping public interfaces stable.

Review Maintenance Changes

Check whether a cleanup remains structural and includes equivalent verification.

Попробуйте эти промпты

Plan a Small Refactor

Use safe-refactor to plan this cleanup. Identify preserved behavior, the smallest structural change, and verification before and after the edit.

Extract Repeated Logic

Extract the repeated logic into one owner. Preserve interfaces, failures, ordering, and compatibility. Keep each intermediate state buildable and testable.

Move an Ownership Boundary

Move this responsibility from the current module to the target module. Separate feature changes and verify every affected public contract.

Design a Staged Refactor

Design staged changes for this cross-package refactor. Define invariants, compatibility constraints, rollback points, and equivalent proof for every stage.

Лучшие практики

Record observable behavior and verification commands before editing.
Move one responsibility at a time and keep every state testable.
Run the same proof after changes and stop when the requested structure is achieved.

Избегать

Mixing new features with structural changes.
Changing public contracts without explicit scope.
Adding dependencies or configuration without a correctness need.

Часто задаваемые вопросы

What counts as a safe refactor?

A safe refactor changes structure while preserving explicitly defined observable behavior.

Does this skill write code?

It guides an agent through scoped structural edits when code and verification tools are available.

Can I change an API during the refactor?

Only when the API change is explicitly scoped. Otherwise, public interfaces should remain stable.

What verification should I use?

Use existing tests, builds, static checks, or focused behavior checks that cover the preserved boundary.

Can this skill add dependencies?

It discourages dependency growth unless a dependency is required for correctness.

When should the refactor stop?

Stop when behavior matches the baseline and the requested structure is achieved.

Сведения для разработчиков

Автор

juliusbrussee

Лицензия

MIT

Ревизия Skillstore

Примечание о версии

Автор не указал версию.

Репозиторий

https://github.com/juliusbrussee/caveman/tree/a0109974ea3258a14aadaef1ed1f8ff2837d30d5/skills/safe-refactor

Ссылка

9e5d158a7fd6576779833ff3529fe92b1a198150

Актуальность поддержки

13.08.2026

Использование

0 загрузок · 0 просмотров

Структура файлов

📁 agents/

📄 openai.yaml

📄 SKILL.md