encore-go-code-review▌
encoredev/skills · updated Apr 8, 2026
When reviewing Encore Go code, check for these common issues:
Encore Go Code Review
Instructions
When reviewing Encore Go code, check for these common issues:
Critical Issues
1. Infrastructure Inside Functions
// WRONG: Infrastructure declared inside function
func setup() {
db := sqldb.NewDatabase("mydb", sqldb.DatabaseConfig{...})
topic := pubsub.NewTopic[*Event]("events", pubsub.TopicConfig{...})
}
// CORRECT: Package level declaration
var db = sqldb.NewDatabase("mydb", sqldb.DatabaseConfig{
Migrations: "./migrations",
})
var topic = pubsub.NewTopic[*Event]("events", pubsub.TopicConfig{
DeliveryGuarantee: pubsub.AtLeastOnce,
})
2. Missing Context Parameter
// WRONG: Missing context
//encore:api public method=GET path=/users/:id
func GetUser(params *GetUserParams) (*User, error) {
// ...
}
// CORRECT: Context as first parameter
//encore:api public method=GET path=/users/:id
func GetUser(ctx context.Context, params *GetUserParams) (*User, error) {
// ...
}
3. SQL Injection Risk
// WRONG: String interpolation
query := fmt.Sprintf("SELECT * FROM users WHERE email = '%s'", email)
rows, err := db.Query(ctx, query)
// CORRECT: Parameterized query
rows, err := sqldb.Query[User](ctx, db, `
SELECT * FROM users WHERE email = $1
`, email)
4. Wrong Return Types
// WRONG: Returning non-pointer struct
//encore:api public method=GET path=/users/:id
func GetUser(ctx context.Context, params *GetUserParams) (User, error) {
// ...
}
// CORRECT: Return pointer to struct
//encore:api public method=GET path=/users/:id
func GetUser(ctx context.Context, params *GetUserParams) (*User, error) {
// ...
}
5. Ignoring Errors
// WRONG: Ignoring error
user, _ := sqldb.QueryRow[User](ctx, db, query, id)
// CORRECT: Handle error
user, err := sqldb.QueryRow[User](ctx, db, query, id)
if err != nil {
return nil, err
}
Warning Issues
6. Not Checking for ErrNoRows
// RISKY: Returns nil without proper error
func getUser(ctx context.Context, id string) (*User, error) {
user, err := sqldb.QueryRow[User](ctx, db, `
SELECT * FROM users WHERE id = $1
`, id)
if err != nil {
return nil, err // ErrNoRows returns generic error
}
return user, nil
}
// BETTER: Check for not found specifically
import "errors"
func getUser(ctx context.Context, id string) (*User, error) {
user, err := sqldb.QueryRow[User](ctx, db, `
SELECT * FROM users WHERE id = $1
`, id)
if errors.Is(err, sqldb.ErrNoRows) {
return nil, &errs.Error{
Code: errs.NotFound,
Message: "user not found",
}
}
if err != nil {
return nil, err
}
return user, nil
}
7. Public Internal Endpoints
// CHECK: Should this cron endpoint be public?
//encore:api public method=POST path=/internal/cleanup
func CleanupJob(ctx context.Context) error {
// ...
}
// BETTER: Use private for internal endpoints
//encore:api private
func CleanupJob(ctx context.Context) error {
// ...
}
8. Non-Idempotent Subscription Handlers
// RISKY: Not idempotent (pubsub has at-least-once delivery)
var _ = pubsub.NewSubscription(OrderCreated, "process-order",
pubsub.SubscriptionConfig[*OrderCreatedEvent]{
Handler: func(ctx context.Context, event *OrderCreatedEvent) error {
return chargeCustomer(ctx, event.OrderID) // Could charge twice!
},
},
)
// SAFER: Check before processing
var _ = pubsub.NewSubscription(OrderCreated, "process-order",
pubsub.SubscriptionConfig[*OrderCreatedEvent]{
Handler: func(ctx context.Context, event *OrderCreatedEvent) error {
order, err := getOrder(ctx, event.OrderID)
if err != nil {
return err
}
if order.Status != "pending" {
return nil // Already processed
}
return chargeCustomer(ctx, event.OrderID)
},
},
)
9. Not Closing Query Rows
// WRONG: Rows not closed
func listUsers(ctx context.Context) ([]*User, error) {
rows, err := sqldb.Query[User](ctx, db, `SELECT * FROM users`)
if err != nil {
return nil, err
}
// Missing: defer rows.Close()
var users []*User
for rows.Next() {
users = append(users, rows.Value())
}
return users, nil
}
// CORRECT: Always close rows
func listUsers(ctx context.Context) ([]*User, error) {
rows, err := sqldb.Query[User](ctx, db, `SELECT * FROM users`)
if err != nil {
return nil, err
}
defer rows.Close()
var users []*User
for rows.Next() {
users = append(users, rows.Value())
}
return users, rows.Err()
}
Review Checklist
- All infrastructure at package level
- All API endpoints have
context.Contextas first parameter - SQL uses parameterized queries (
$1,$2, etc.) - Response types are pointers
- Errors are handled, not ignored
-
sqldb.ErrNoRowschecked where appropriate - Internal endpoints use
privatenotpublic - Subscription handlers are idempotent
- Query rows are closed with
defer rows.Close() - Migrations follow naming convention (
1_name.up.sql)
Output Format
When reviewing, report issues as:
[CRITICAL] [file:line] Description of issue
[WARNING] [file:line] Description of concern
[GOOD] Notable good practice observed
Ratings
4.6★★★★★30 reviews- ★★★★★Shikha Mishra· Dec 16, 2024
encore-go-code-review reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Yash Thakker· Nov 7, 2024
I recommend encore-go-code-review for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Dhruvi Jain· Oct 26, 2024
Useful defaults in encore-go-code-review — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Oshnikdeep· Sep 17, 2024
encore-go-code-review has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Min Harris· Sep 1, 2024
Solid pick for teams standardizing on skills: encore-go-code-review is focused, and the summary matches what you get after install.
- ★★★★★Yuki Ndlovu· Sep 1, 2024
Registry listing for encore-go-code-review matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Nia Ghosh· Aug 20, 2024
encore-go-code-review has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Advait Sethi· Aug 20, 2024
encore-go-code-review reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Ganesh Mohane· Aug 8, 2024
Solid pick for teams standardizing on skills: encore-go-code-review is focused, and the summary matches what you get after install.
- ★★★★★Rahul Santra· Jul 27, 2024
We added encore-go-code-review from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
showing 1-10 of 30