fixme-config

Edit .fixme/config.json for fixme pipelines, model profiles, and Linear integration.

Updated Feb 18, 2026
One-click install
npx skills add https://github.com/denis-pingin/fixme --skill fixme-config
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fixme-config
Source: https://github.com/denis-pingin/fixme/tree/main/.claude/skills/fixme-config
Command: npx skills add https://github.com/denis-pingin/fixme --skill fixme-config

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Interactive configuration for fixme pipelines, model profiles, project settings, and Linear integration. Creates or updates .fixme/config.json.

Core Features & Use Cases

  • Interactive onboarding for fixme settings (model profiles, pipelines, ticket backend) and auto-merge with existing configuration.
  • Guided, validation-driven edits for project commands, framework, and Linear integration when needed.
  • Use Case: A team wants a consistent default pipeline and a Linear-backed ticket backend across multiple projects.

Quick Start

Run the fixme-config skill with an init to begin interactive setup and save your .fixme/config.json.

Frequently Asked Questions about fixme-config

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

FAQPage Schema
How do I configure fixme pipelines and Linear integration for my project?

You configure fixme pipelines and Linear integration by editing the .fixme/config.json file through a guided, interactive session that sets defaults for model profiles, project commands, and ticket backends.

What is a .fixme/config.json file used for?

The .fixme/config.json file stores default settings for fixme pipelines, model profiles, project frameworks, and Linear ticket backend integration, ensuring consistent configuration across multiple projects.

Can I update existing fixme settings without overwriting my current model profiles?

Yes, the interactive configuration session performs validation-driven edits and auto-merges new settings with your existing .fixme/config.json, ensuring current model profiles and pipeline defaults are safely preserved.

How do I set up a Linear-backed ticket backend across multiple projects?

You set up a Linear-backed ticket backend by running an interactive onboarding session that configures Linear integration and persists the default pipeline settings to .fixme/config.json for consistent multi-project use.

Does fixme config editing require manual JSON validation?

No, the configuration process satisfies validation and safe-merge requirements automatically, verifying which keys are updated and persisting changes to .fixme/config.json using the Write tool without manual JSON validation.

When should I use interactive configuration instead of manually editing project settings?

You should use interactive configuration when you need guided, validation-driven edits for project commands, frameworks, or Linear integration, ensuring safe-merge requirements are met without risking invalid JSON formatting.