Fix Gosec Bug From Issue
Testing & QualityFix Gosec Bug From Issue is an Agent Skill for testing & quality published in the securego/gosec repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Analyze, reproduce, and fix a gosec bug reported in a GitHub issue with a confirmation-gated workflow.
QUICK START
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/securego/gosec/blob/HEAD/.github/skills/gosec-fix-issue/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/fix-gosec-bug-from-issue, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Fix a gosec bug from a GitHub issue
Use this skill when you want to fix a bug described in a GitHub issue.
Required input
Provide at least:
- GitHub issue URL
Optional but useful:
- gosec version
- Go version (
go versionoutput) - OS and environment details
- extra reproduction notes
Execution workflow
- Review the GitHub issue thoroughly and extract the problem statement, reproduction hints, expected behavior, and actual behavior.
- Try to reproduce the issue against the current
masterversion of gosec. - Analyze the codebase and isolate the root cause.
- Produce a detailed, minimal fix plan and stop. Ask for confirmation before changing code.
After confirmation, implement end-to-end:
- Keep the fix small and isolated to the issue scope.
- Follow good design principles and idiomatic Go.
- Add tests for both positive and negative cases.
- When a code sample is appropriate, add or update a sample in
testutils/in the relevant rule sample file. - Validate the result:
- Build succeeds
- Relevant tests pass
golangci-linthas no warnings in changed codegosecCLI run on a sample confirms the issue is fixed
Output requirements
- First response must only contain:
- Reproduction status on
master(or clear blocker) - Root cause analysis
- Detailed fix plan
- Confirmation request
- Reproduction status on
- Do not implement any code changes until confirmation is provided.