dev-structured-logs
Migrate legacy string-based logging in .NET/C# code to structured logging templates, insert CommandHandler logging scopes, and validate or update Serilog File sink settings in appsettings JSON files. Use when users ask to modernize ILogger or Serilog usage through safe rewrites, run dry-run logging migration previews, apply structured logging rewrites, or enforce JSON file sink formatter and path conventions. For general backend design and observability guidance use $software-csharp-backend, for NUnit test design use $qa-testing-nunit, and for pipeline changes use $ops-nuke-cicd.
What this skill does
# Structured Logs
Run conservative, review-friendly rewrites for legacy log calls and Serilog JSON config. Default to dry-run and always produce machine-readable preview output.
This is an operation skill for deterministic logging rewrites. Do not use it as a general backend observability or CI/CD guidance skill.
## Workflow
1. Run dry-run first:
```bash
python .codex/skills/dev-structured-logs/scripts/structured_logs.py --path <repo> --dry-run
```
2. Review:
- `<repo>/patch.diff`
- `<repo>/preview-report.json`
3. Apply only after review:
```bash
python .codex/skills/dev-structured-logs/scripts/structured_logs.py --path <repo> --apply --backup-dir <dir>
```
4. Optionally commit:
```bash
python .codex/skills/dev-structured-logs/scripts/structured_logs.py --path <repo> --apply --commit-msg "chore: structured logging migration"
```
If the task expands into service design, runtime observability strategy, or API-layer refactoring, switch to `$software-csharp-backend`.
If the task expands into `nuke/Build.cs` or CI execution changes, switch to `$ops-nuke-cicd`.
## CLI Contract
Support these options:
```bash
--path <repo>
[--dry-run]
[--apply]
[--preview-file <path>]
[--backup-dir <dir>]
[--enable-handler-scope]
[--handler-pattern <pattern>]
[--log-framework <serilog|microsoft|auto>]
[--exclude <glob>] (repeatable)
[--commit-msg "message"]
```
Behavior:
- Default mode is dry-run when `--apply` is not provided.
- CommandHandler scope insertion is disabled by default; enable it explicitly with `--enable-handler-scope`.
- Do not touch excluded/generated folders: `bin/`, `obj/`, `node_modules/`, `packages/`, `.git/`, `.vs/`.
- Flag risky rewrites in `preview-report.json` with `risk_level` and `reason`.
## Part 1: Logging Transformation Rules
Rewrite only `logger.Log*` and `_logger.Log*` style invocations where message argument uses:
- String concatenation
- `String.Format(...)`
- String interpolation (`$"..."`)
Transform to message templates with properties and argument list.
Preserve interpolation expressions as argument expressions (including ternary expressions).
Preserve:
- Exception overload ordering (`LogError(ex, "...", args...)`)
- Original expression order
If any message argument has potential side effects (method call, `new`, increment/decrement, compound assignment):
- Extract expression to temporary variable before logging call
- Mark change as manual review in report
Do not attempt risky cross-statement rewrites. Keep changes local to call sites.
## Part 2: CommandHandler Scope Rules
Detect handlers by either:
- Class implementing `ICommandHandler<T>`
- Public methods matching handler pattern (default `Handle|HandleAsync`) with first parameter treated as command object
When `--enable-handler-scope` is set, at method start insert scope when missing:
- Build dictionary from command key properties: `UserId`, `TransactionId`, `TransferId`, `VerificationId`, `SessionId`, `Id`
- Initialize scope items with dictionary collection initializer style, for example:
```csharp
var __scopeItems = new Dictionary<string, object>
{
["Property1"] = command.Property1
};
```
- Use `using var _scope = _logger.BeginScope(__scopeItems);`
Skip if an equivalent command-property `BeginScope` block already exists in method prologue.
## Part 3: Serilog appsettings Rules
Auto-detect Serilog via `*.csproj` package references containing `Serilog`, `Serilog.*`, or `Sc.Infrastructure.Serilog`.
If any `*.csproj` file contains one of those package names, treat repository as Serilog-enabled and apply Serilog configuration updates to all `appsettings.json` files in the repository.
If Serilog is detected, inspect all `appsettings.json` files in the repository.
For each Serilog `File` sink with object `Args` (including nested `WriteTo` pipelines such as `Async` -> `Logger` -> `configureLogger` -> `WriteTo`):
- Ensure `Args.path` ends with `.json`
- If `Args.path` is a debug log file path (for example `*.debug`), rename it to `.debug.json`
- Set `Args.formatter` to:
- `Sc.Infrastructure.Serilog.CustomJsonFormatter, Sc.Infrastructure.Serilog`
- Remove `Args.outputTemplate`
Do not modify non-File sinks.
If Serilog section or File sink does not exist, do nothing.
## Outputs
Always produce in repo root:
- `patch.diff` unified diff
- `preview-report.json` entries:
- `file`
- `line`
- `original`
- `transformed`
- `risk_level`
- `reason`
When applying:
- Create backups in `--backup-dir` or `.codex/skills/dev-structured-logs/backups`
- Apply file updates
- If `--commit-msg` is supplied, attempt git commit
## Examples
Use files in `examples/` to validate behavior:
- `concatenation.before.cs` / `concatenation.after.cs`
- `string-format.before.cs` / `string-format.after.cs`
- `interpolation.before.cs` / `interpolation.after.cs`
- `side-effect.before.cs` / `side-effect.after.cs`
- `handler-scope.before.cs` / `handler-scope.after.cs`
- `appsettings.before.json` / `appsettings.after.json`
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.