kokatsu/logging

Logging Skill

Review or implement proper application logging based on established guidelines.

Respond to the user in the same language they use.

Usage

/logging [file path, directory, or description]

Arguments

• $ARGUMENTS: File path, directory, or description of the analysis target (optional)
  • If omitted: Ask the user what to analyze

Workflow

1. Read guidelines — Load ${CLAUDE_SKILL_DIR}/guidelines.md
2. Detect existing setup — Identify the project's logging library, format, and conventions. Existing project conventions take precedence over guidelines — never introduce a new logging style that conflicts with what the project already uses.
3. Identify target — Determine which files/modules to analyze based on $ARGUMENTS
4. Analyze — Check logging against guidelines (5W1H, level appropriateness, security)
5. Determine mode:
   • Review mode: User asks to "review", "check", "audit", or phrases the request as a question (e.g., "ログ大丈夫？", "logging issues?"). Default when intent is unclear.
   • Implement mode: User explicitly asks to "add", "fix", "implement", "improve", or "replace" logging.
6. Act — Report issues (review) or add/fix logging (implement)

Critical Rules

• Security findings are highest priority — Sensitive data leaks (passwords, tokens, PII) must be flagged before any other issue
• Review mode does not modify code — Report findings only; never edit files unless explicitly asked to implement
• Respect existing conventions — Adapt guidelines to the project's language, logging library, and style. Do not introduce a different library or format without the user's explicit approval

Output

Review mode

Report findings as a table:

| File:Line | Severity | Issue | Recommendation | |---|---|---|---| | auth.py:42 | HIGH | Password logged in plain text | Remove password from log fields |

Implement mode

1. Make changes following guidelines and existing project conventions
2. Verify: build passes, existing tests unaffected
3. Summarize what was added/modified