Menu
Insert consistent method/step structured logging lines into target functions using jig.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
When the user wants to codify a repeatable code generation pattern into a jig recipe — design variables, choose operations (create/inject/patch/replace), write Jinja templates, and validate the result. Use when someone says "I keep writing this same boilerplate", "make a recipe for X", or wants to turn a manual edit into an automated pattern.
When the user needs to chain multiple jig recipes into a multi-step workflow with conditional execution and shared variables. Use when a pattern spans multiple files that need coordinated creation and modification, like scaffolding an entire endpoint or a full feature slice.
Scaffold queryset/manager/selector layers and wire view reads through selector entrypoints with jig.
Generate two-step rollout-safe Django migrations plus model-field patching using jig.
Write deterministic service tests with stable fixtures and boundary mocks without using jig.
Keep reads in selectors/querysets and keep write logic in services without using jig.
| name | structured-logging-contract |
| description | Insert consistent method/step structured logging lines into target functions using jig. |
Use this skill to enforce stable observability signals.
target_filefunction_nameevent_namespacestep_nameentity_id_exprjig run ${CLAUDE_SKILL_DIR:-.claude/skills/structured-logging-contract}/recipe.yaml --vars '{
"target_file": "services/core_service.py",
"function_name": "create_record",
"event_namespace": "core_service.create_record",
"step_name": "validate_input",
"entity_id_expr": "record_id if \"record_id\" in locals() else None"
}'
Notes:
function_name anchor directly..done event is inserted immediately before the return { line via a direct before selector.