add-config-field

Add a configuration field across TypeScript interfaces, defaults, and wiring.

Updated Jan 30, 2026
One-click install
npx skills add https://github.com/martin-janci/claude-code-reviewer --skill add-config-field
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-config-field
Source: https://github.com/martin-janci/claude-code-reviewer/tree/main/.claude/skills/add-config-field
Command: npx skills add https://github.com/martin-janci/claude-code-reviewer --skill add-config-field

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guide helps developers add a new configuration field across interfaces, defaults, and wiring in the claude-code-reviewer project, ensuring consistent integration.

Core Features & Use Cases

  • Gather requirements from stakeholders and surface the exact field name, type, default, and wiring points.
  • Show current implementations across interfaces (src/types.ts), defaults (src/config.ts), and config documentation (config.yaml) to ensure consistency.
  • Produce an exact implementation checklist with file paths and required edits to add the field, including optional PRState and ReviewRecord considerations.

Quick Start

Provide an implementation checklist with exact file locations to add a new config field across the claude-code-reviewer project.

Frequently Asked Questions about add-config-field

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a new configuration field across TypeScript interfaces and defaults?

To add a new config field across TypeScript interfaces and defaults, update src/types.ts for the interface, src/config.ts for default values, and config.yaml for documentation to ensure consistent wiring and integration.

What files do I need to modify to add environment overrides for a config field?

Adding environment overrides for a config field requires modifying src/types.ts for the interface, src/config.ts for default wiring and environment overrides, config.yaml for documentation, and optionally updating state management records.

When do I need to update PRState and ReviewRecord when modifying config.yaml?

You update PRState and ReviewRecord when the new configuration field must persist across per-PR state or review records, ensuring the state management layer accurately tracks the newly added config value.

Can I use this guide to wire config defaults for a TypeScript code reviewer project?

Yes, this guide is specifically designed for the claude-code-reviewer project, providing an exact implementation checklist with file paths to wire config defaults across TypeScript interfaces, config.yaml, and state management.

What is the best way to ensure consistent integration when adding a new config field?

The best way to ensure consistent integration is to follow a reproducible implementation checklist that targets canonical locations like src/types.ts, src/config.ts, and config.yaml, covering interfaces, defaults, environment overrides, and state updates.