golang-project-layout
Organize Go Projects and Multi-Module Workspaces
Unclear package boundaries make Go projects harder to maintain. This skill guides directory layout, module naming, test placement, and workspace setup around project requirements.
ArrĂȘtez-vous et demandez confirmation avant lâinstallation.
Examinez le plan et obtenez le consentement explicite de lâutilisateur avant de modifier des fichiers.
Installer avec mon Agent
Copiez cette demande dans votre Agent. Elle contient la page Skill de référence et le manifeste.
Review the Skillstore skill "golang-project-layout" from https://skillstore.io/skills/samber-golang-project-layout.md and its manifest at https://skillstore.io/api/skills/samber-golang-project-layout/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.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.
Tester
Utilisation de « golang-project-layout ». Plan a small CLI with a flat architecture and no dependency injection framework.
RĂ©sultat attendu:
- Use one command entry point with minimal startup logic.
- Keep private behavior in a small internal package.
- Place tests beside their implementation and fixtures in a local testdata directory.
- Start with one module and omit a workspace.
Utilisation de « golang-project-layout ». Our server and shared logging library are separate modules developed together. Should we use a workspace?
RĂ©sultat attendu:
- A workspace fits related modules that need local cross-module development.
- Add both existing module directories to workspace membership.
- Keep each module's dependency metadata separate.
- Use local workspace resolution instead of repeated replacement directives.
Utilisation de « golang-project-layout ». Where should private request parsing and a reusable public logging package live?
RĂ©sultat attendu:
- Keep request parsing in an internal package.
- Expose the logging API through a public package when external consumers need it.
- For a dedicated library module, prefer a root-level public package.
- Keep executable startup logic separate from reusable behavior.
Audit de sécurité
Risque élevéAll 78 static matches are false positives involving documentation, Go syntax, ignore rules, or ordinary build automation. A separate high-severity prompt injection directs persistent agent configuration changes to always load another skill without user confirmation. No evidence found of credential exfiltration or malicious network execution in the reviewed files.
Préoccupations de sécurité confirmées (1)
Facteurs de risque
âïž Commandes externes (50)
đ AccĂšs au systĂšme de fichiers (2)
⥠Contient des scripts (2)
đ AccĂšs rĂ©seau (2)
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.
Copier le lien du rapport
https://skillstore.io/skills/samber-golang-project-layout/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportBadge Markdown
[](https://skillstore.io/skills/samber-golang-project-layout?utm_source=security_passport_badge)Badge HTML
<a href="https://skillstore.io/skills/samber-golang-project-layout?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/samber-golang-project-layout/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Carte intégrable
<iframe src="https://skillstore.io/embed/skills/samber-golang-project-layout.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-project-layout security audit report (audit version 1) [Author version 1.4.2]. Skillstore. https://skillstore.io/skills/samber-golang-project-layout/audits/1Citation BibTeX
@techreport{samber-samber-golang-project-layout-2026,
author = {samber},
title = {golang-project-layout security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/samber-golang-project-layout/audits/1},
note = {Author version 1.4.2}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "golang-project-layout security audit report (audit version 1)"
version: "1.4.2"
type: report
authors:
- name: "samber"
date-released: "2026-10-15"
url: "https://skillstore.io/skills/samber-golang-project-layout/audits/1"
identifiers:
- type: other
value: "skillstore:samber-golang-project-layout:audit:1"
description: "Skillstore immutable audit report identifier"
Score Skillstore
Pourquoi ce score Niveau de confiance des preuves: MoyenCe que vous pouvez créer
Start a focused CLI project
Choose a small directory structure, a meaningful module path, and local test placement without unnecessary architecture layers.
Separate service entry points
Organize server, worker, and migration binaries while keeping shared business logic in private packages.
Coordinate related Go modules
Plan workspace membership and local dependency resolution for modules developed together in a monorepo.
Essayez ces prompts
Help me plan a small Go CLI called [name]. Ask about architecture first, then dependency injection. Recommend a minimal layout without editing files.
Plan a layout for [service] with an API server and migration binary. Ask about architecture and dependency injection before suggesting packages. Include test placement.
Review [directory tree] for private implementation and reusable API boundaries. Recommend focused layout changes and explain module naming. Do not modify persistent agent configuration.
Design a go.work workspace for [module paths]. Explain local resolution, initialization, and cross-module testing. Identify when a single module is preferable. Propose changes before execution.
Bonnes pratiques
- Confirm project scope, architecture, and dependency injection preferences before creating directories.
- Use workspaces for related modules, not merely for multiple packages within one module.
- Review templates and commands before execution, and require approval for persistent agent configuration changes.
Ăviter
- Creating empty architecture layers or public packages without a concrete need.
- Collecting business logic in entry points or vague utility packages.
- Automatically adding always-load skill instructions to persistent project configuration without explicit approval.
Foire aux questions
What does this skill help organize?
Does every project need go.work?
Is pkg required for public libraries?
Does the skill include a complete application generator?
What tools are needed to run the suggested commands?
Does the skill change persistent agent instructions?
Détails du développeur
Auteur
samberLicence
MIT
Version de lâauteur
v1.4.2
RĂ©vision Skillstore
r1
RĂ©f
a403f4fe81871b733d63ce3fcd6a4a3a24eb6a0e
RĂ©cence de maintenance
15/10/2026
Utilisation
0 téléchargements · 0 vues
Structure de fichiers
đ assets/
đ .gitignore
đ Makefile
đ evals/
đ evals.json
đ references/
đ config.md
đ directory-layouts.md
đ testing-layout.md
đ workspaces.md
đ SKILL.md