Coding
PromptBeginner5 minmarkdown
Nano Banana Pro
Agent skill for nano-banana-pro
7
This guide explains how to work effectively inside the RISKEN AWS codebase. Follow these practices to keep builds green and releases predictable.
Sign in to like and favorite skills
This guide explains how to work effectively inside the RISKEN AWS codebase. Follow these practices to keep builds green and releases predictable.
cmd/<service>/: main packages for each scanner entrypoint (access-analyzer, admin-checker, cloudsploit, guard-duty, portscan).pkg/<service>/ and pkg/common/: shared service logic, helpers, and gRPC/SQS clients; business code lives here.dockers/ holds container build contexts; hack/ scripts automate image builds; codebuild/ contains CI specs.docs/ and testdata/ store reference material and fixtures—extend them instead of creating ad-hoc folders.cloudsploit.yaml should remain templates; keep environment secrets in local overrides excluded by .gitignore.make build IMAGE_TAG=dev: runs go test then builds every service image via hack/docker-build.sh.make go-test: executes go generate and go test ./...; run before any push.make lint: invokes golangci-lint (5m timeout) with GOFLAGS=-buildvcs=false.make generate: refreshes protobufs and other generated assets.make enqueue-*); point AWS CLI at http://localhost:9324.gofmt/goimports (tabs, concise camelCase names). CI fails unformatted code.pkg/common/logging for structured logs and envconfig structs for configuration parsing._test.go files beside source; pull fixtures from testdata/.pkg/... so unit tests remain deterministic; avoid calling live AWS endpoints.make go-test; add focused integration cases guarded by build tags if external services are required.feat:, fix:, chore:); keep subjects imperative and ≤72 characters.make go-test and make lint succeed; request review from a RISKEN AWS maintainer and include image/tag notes when touching dockers/ or deployment manifests.cloudsploit.yaml, enqueue payloads).localhost resources to prevent unintended production calls.