Compétences golang-refactoring

📦

golang-refactoring

Name: golang-refactoring
Author: samber

v1.1.1 Révision du contenu r1 Sûr 📁 Accès au système de fichiers⚡ Contient des scripts⚙️ Commandes externes🌐 Accès réseau

Refactor Go Code with Tests and Human Review

Large Go refactors can break callers, hide behavior changes, and create conflicting pull requests. This skill guides tool-driven changes with targeted tests and staged human review.

Prend en charge: Codex Code(CC)

🥉 78 Bronze

Maintain this Skill? Claim it 🥉 78 Bronze

Installer avec mon Agent

Copiez cette demande dans votre Agent. Elle contient la page Skill de référence et le manifeste.

Demande d’agent

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

Votre Agent doit toujours présenter son plan et demander toute confirmation exigée par la politique de sécurité.

Ressources lisibles par les agents

Utilisez ces liens lorsqu’un Agent IA, un crawler ou un script a besoin d’un contexte propre au lieu de lire toute la page.

Détail Markdown GET /skills/samber-golang-refactoring.md manifest signé GET /api/skills/samber-golang-refactoring/manifest lockfile signé GET /api/skills/samber-golang-refactoring/lockfile

Tester

Utilisation de « golang-refactoring ». Plan extracting validation from a long order-processing function with limited tests.

Résultat attendu:

Assessment: affected validation paths need characterization tests before extraction.
Plan: capture current success and failure results, then extract only the validation responsibility.
Verification: review the extraction diff and run build, vet, and targeted tests.
Checkpoint: obtain approval before editing; keep behavior changes outside this refactor.

Utilisation de « golang-refactoring ». Plan moving a public invoice type into a billing package without breaking callers.

Résultat attendu:

Assessment: inspect callers, package dependencies, exported methods, and reflection-sensitive uses.
Stage one: introduce the type in the destination and preserve the old name through a compatibility alias.
Stage two: migrate callers incrementally in reviewed pull requests.
Stage three: remove the deprecated alias only after reference checks and the required compatibility review.

Audit de sécurité

Sûr

v1 • 18/10/2026 Ouvrir le rapport versionné

All 52 static findings are false positives involving Markdown formatting, documentation links, Go examples, or legitimate refactoring tools. No evidence found of malicious prompt injection, credential theft, or unauthorized data transfer in the six reviewed files. Tool installation, repository edits, test execution, and pull request creation remain operational actions requiring appropriate permissions and review.

Fichiers analysés

1,008

Lignes analysées

Éléments à examiner

Faux positifs ignorés

Facteurs de risque

📁 Accès au système de fichiers (3)

references/catalog.md:3 references/go-tooling.md:22 references/safety-net.md:80

⚡ Contient des scripts (1)

references/go-tooling.md:52-55

⚙️ Commandes externes (31)

🌐 Accès réseau (2)

SKILL.md:12 SKILL.md:159

Le dernier audit statique et sémantique terminé n’a détecté aucun constat de sécurité confirmé. Cela ne prouve pas que le skill est sans effets secondaires.

Audité par: codex

Partager et citer ce rapport

Partagez le rapport d’évaluation versionné, le badge neutre, la carte intégrable et les citations. Skillstore présente les preuves sans décider si ce Skill est sûr.

Ouvrir le rapport versionné

Copier le lien du rapport

https://skillstore.io/skills/samber-golang-refactoring/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Badge Markdown

[![Skillstore security assessment](https://skillstore.io/badges/skills/samber-golang-refactoring/security.svg)](https://skillstore.io/skills/samber-golang-refactoring?utm_source=security_passport_badge)

Badge HTML

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

Carte intégrable

<iframe src="https://skillstore.io/embed/skills/samber-golang-refactoring.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Citations académiques (APA · BibTeX · CFF)

Citation APA

samber. (2026). golang-refactoring security audit report (audit version 1) [Author version 1.1.1]. Skillstore. https://skillstore.io/skills/samber-golang-refactoring/audits/1

Citation BibTeX

@techreport{samber-samber-golang-refactoring-2026,
  author = {samber},
  title = {golang-refactoring security audit report (audit version 1)},
  institution = {Skillstore},
  year = {2026},
  number = {1},
  url = {https://skillstore.io/skills/samber-golang-refactoring/audits/1},
  note = {Author version 1.1.1}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "golang-refactoring security audit report (audit version 1)"
version: "1.1.1"
type: report
authors:
  - name: "samber"
date-released: "2026-10-18"
url: "https://skillstore.io/skills/samber-golang-refactoring/audits/1"
identifiers:
  - type: other
    value: "skillstore:samber-golang-refactoring:audit:1"
    description: "Skillstore immutable audit report identifier"

Score Skillstore

Pourquoi ce score Niveau de confiance des preuves: Moyen

Architecture

100

Maintenabilité

Contenu

Communauté

Conformité aux spécifications

Ce que vous pouvez créer

Split an Overgrown Function

Assess affected code, add missing tests, and extract a focused helper without combining the change with a feature.

Migrate a Shared Package

Plan compatibility aliases, caller migration, dependency ordering, and staged reviews for a type moved between packages.

Coordinate a Multi-Step Refactor

Build a change inventory, isolate worktrees, and schedule independent pull requests without parallelizing overlapping symbol edits.

Essayez ces prompts

Review a Small Rename

Inspect [symbol] and propose a safe rename to [new name]. Identify references, reflection risks, and verification steps. Wait for approval before editing.

Extract a Tested Helper

Plan extracting [responsibility] from [function]. Measure affected coverage, propose missing tests, and choose a gopls action. Present the plan before changing code.

Move a Public Type

Plan moving [type] from [old package] to [new package]. Include aliases, import-cycle checks, external caller risks, and incremental migration checkpoints.

Stage a Repository Refactor

Create an inventory for [refactoring goal]. Classify risk and structural versus behavioral changes. Order dependencies, identify parallel work, and define tests and approval gates.

Bonnes pratiques

Approve a refactoring inventory before editing and request new approval when the scope or risk changes.
Measure coverage on affected paths and add characterization tests before restructuring poorly tested code.
Keep each change atomic, inspect tool-generated diffs, and verify build, tests, reflection-sensitive references, and relevant benchmarks.

Éviter

Mixing a rename or package move with a bug fix or feature in the same pull request.
Running a workspace-wide rename concurrently with other changes that could touch the same symbols.
Treating passing tests or a mechanical rewrite as proof that reflection, external consumers, and security behavior remain unchanged.