smykla-skalski/go-code-review
codex/go-code-review/SKILL.md
Review Go code using the source material under `claude/go-code-review`. Use when the user wants a focused Go review grounded in known failure patterns.
$ install --global
skillsauthnpx skillsauth add smykla-skalski/sai go-code-reviewInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 26, 2026, 8:05 AM43.8s2 files scanned
SKILL.md
- name:
- go-code-review
- description:
- Review Go code using the source material under `claude/go-code-review`. Use when the user wants a focused Go review grounded in known failure patterns.
- short-description:
- Review Go code for common mistakes
Go Code Review
Use this skill when reviewing Go code and the user wants a focused quality review.
This is a thin Codex wrapper around claude/go-code-review/skills/go-code-review/SKILL.md. Reuse the source workflow, references, scripts, and eval material from the Claude skill directory instead of maintaining duplicated Codex copies.
Use This Skill
- Use this skill when reviewing Go code and the user wants a focused quality review.
Do Not Use This Skill
- Do not use this skill for non-Go review or for broad architectural review better handled elsewhere.
Source Material
- Source skill:
claude/go-code-review/skills/go-code-review/SKILL.md - Source directory:
claude/go-code-review/skills/go-code-review/ - Codex metadata:
agents/openai.yaml
Load only the source files needed for the current task. Do not recreate or copy the Claude-side bundled resources into this Codex skill.
Workflow
- Treat
claude/go-code-review/skills/go-code-review/SKILL.mdas the source workflow. - Read
claude/go-code-review/skills/go-code-review/knowledge-base.mdbefore reviewing. - Use
real-world-patterns.mdorevals/test-cases.mdfrom the same source directory only when they materially improve the review. - Report findings first, ordered by severity, with concrete file evidence.
Codex Notes
- Ignore Claude-only frontmatter and runtime wiring such as
allowed-tools,user-invocable,$ARGUMENTS, andCLAUDE_SKILL_DIR. - Infer inputs from the user request and local context before asking follow-up questions.
- If a source script or networked command fails because of sandbox restrictions, rerun it with escalation and a short justification.
- For destructive or irreversible actions, confirm intent unless the user was already explicit.
Verification
After any fix or state-changing action, rerun the narrowest relevant validator, script, listing command, or source check and compare the before/after result.
- Re-check the key output, diff, command result, or rendered text after you act.
- If the task changed files or external state, rerun the narrowest relevant validator, script, listing command, or source query.
- Report what was verified, what remains unverified, and any residual risk.
Examples
<example> User: "Use Go Code Review for this task." Assistant: Opens `claude/go-code-review/skills/go-code-review/SKILL.md`, loads only the needed source references or scripts, adapts the workflow to Codex conventions, and completes the task. </example> <example> User: "Apply the Go Code Review workflow here." Assistant: Reuses the source material from `claude/go-code-review/skills/go-code-review/` instead of relying on duplicated Codex-side resources. </example>Related Skills
smykla-skalski/council
development
VerifiedTrustedCommunity
Run the council workflow from a normal Copilot session only when the user explicitly asks for council review, multi-persona critique, debate, design review, code review, architecture feedback, UX review, or tradeoff analysis. Do not use it for commit, stage, merge, approval, or generic pre-commit requests. Accept the same mode syntax as the bundled council reviewers: `core|auto|core-eng|core-ux|core-mix|all|debate <problem|@file>`. During council slash-command use, the current session agent moderates reviewer agents directly. Runs broader than 6 reviewers require explicit AskUserQuestion approval before launch.
2SKILL.mdUpdated Apr 30, 2026
smykla-skalski/council
tools
VerifiedTrustedCommunity
Use when the user invokes $council, $council:council, Council review, or Council debate. Use loaded SKILL body or one direct installed `skills/council/SKILL.md` read. Direct read path must contain `/.codex/plugins/cache/sai/council/` and end `/skills/council/SKILL.md`. `cd <cwd> && sed -n ... <path>` is valid. Do not use `pwd`, `ls`, `find`, `rg`, `cat`, multiple `&&`, or `;`. Never use repo-local paths. If unavailable, stop exactly `Council not run: skill unavailable.` At most one pre-tool message, exact `Council progress:` line only. Non-final lines start `Council progress:`.
2SKILL.mdUpdated Apr 29, 2026
smykla-skalski/council
development
VerifiedTrustedCommunity
Run council reviews with sourced engineering, UX, reliability, performance, AI, and strategy persona lenses. Use when the user asks for council review, multi-persona critique, debate, design review, code review, architecture feedback, UX review, or tradeoff analysis.
2SKILL.mdUpdated Apr 29, 2026
smykla-skalski/council
development
VerifiedTrustedCommunity
Use when the user asks for council review, multi-persona critique, debate, design review, code review, architecture feedback, UX review, or tradeoff analysis. Bare invocations use `core` profile auto-detect; explicit `auto` selects the best-fit 6 personas from the sourced 27-persona engineering and UX roster. Users can still pin `core`, `core-eng`, `core-ux`, `core-mix`, `all`, or `debate`.
2SKILL.mdUpdated Apr 29, 2026