solace-broker-mcp: Skill for Claude Code

Add Logs

Add structured log/slog logging to Go code that follows the project's secure logging rules. Invoked with /add-logs.

When to use

• After implementing a new feature or function that needs logging
• When migrating log.Printf calls to slog
• When adding logging to an existing file that lacks it

Usage

• /add-logs <file_path> — add logging to a specific file
• /add-logs <file_path> <function_name> — add logging to a specific function

If invoked without arguments, ask the user which file or function to target.

Steps

Step 1: Read the rules

Read the secure logging rules at docs/secure-logging-rules.md in the project root. These rules are non-negotiable — every log line you write must comply.

Step 2: Read the target code

Read the file or function the user specified. Understand what it does, what events are significant, and what data flows through it.

Step 3: Identify loggable events

For each function, identify events that belong in the Always-Log list from the rules:

• Server startup/shutdown
• Tool invocations (tool name, broker alias, outcome, duration_ms)
• Tool errors (tool name, broker alias, error_type, http_status)
• Broker connections created (broker alias, URL)
• Config loaded (broker_count, port)
• Any error or failure path

Step 4: Write the log calls

For each event, write a slog call following these constraints:

Always:

• Use slog.Info(), slog.Warn(), or slog.Error() — not log.Printf
• Use structured fields: slog.String("key", value), slog.Int("key", value), slog.Duration("key", value)
• Keep the message string static and descriptive (no variable data in the message)
• Include all required fields from the Always-Log table

Never:

• Never log anything on the Never-Log list (passwords, usernames, tokens, auth headers, raw config maps, URLs with embedded credentials)
• Never use fmt.Sprintf in the message string with external data
• Never log raw structs with slog.Any("key", someStruct) — log explicit fields
• Never log raw err.Error() from external systems (SEMP, HTTP) without reviewing what it could contain
• Never log to stdout — always stderr