fix-bug — community fix-bug, formidable-forms, community, ide skills

v1.0.0

About this Skill

Perfect for Developer Agents needing structured bug-fixing workflows for WordPress and Formidable Forms plugin ecosystems. Bug-fixing workflow for Formidable Forms. Use when fixing bugs, debugging unexpected behavior, investigating error logs, or resolving compatibility issues.

Strategy11 Strategy11
[60]
[39]
Updated: 2/26/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reviewed Landing Page Review Score: 9/11

Killer-Skills keeps this page indexable because it adds recommendation, limitations, and review signals beyond the upstream repository text.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution Quality floor passed for review Locale and body language aligned
Review Score
9/11
Quality Score
53
Canonical Locale
en
Detected Body Locale
en

Perfect for Developer Agents needing structured bug-fixing workflows for WordPress and Formidable Forms plugin ecosystems. Bug-fixing workflow for Formidable Forms. Use when fixing bugs, debugging unexpected behavior, investigating error logs, or resolving compatibility issues.

Core Value

Empowers agents to follow WordPress and WordPress VIP coding standards, utilizing always-on rules in .windsurf/rules/enterprise/ for core principles, code change phases, writing style, and commit message format, ensuring high-quality bug fixes.

Ideal Agent Persona

Perfect for Developer Agents needing structured bug-fixing workflows for WordPress and Formidable Forms plugin ecosystems.

Capabilities Granted for fix-bug

Debugging reported bugs in Formidable Forms plugins
Fixing unexpected behavior in WordPress environments
Implementing automated testing for bug fixes

! Prerequisites & Limits

  • Requires knowledge of WordPress and Formidable Forms plugin ecosystems
  • Limited to bug-fixing workflows for these specific ecosystems

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is fix-bug?

Perfect for Developer Agents needing structured bug-fixing workflows for WordPress and Formidable Forms plugin ecosystems. Bug-fixing workflow for Formidable Forms. Use when fixing bugs, debugging unexpected behavior, investigating error logs, or resolving compatibility issues.

How do I install fix-bug?

Run the command: npx killer-skills add Strategy11/formidable-forms/fix-bug. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for fix-bug?

Key use cases include: Debugging reported bugs in Formidable Forms plugins, Fixing unexpected behavior in WordPress environments, Implementing automated testing for bug fixes.

Which IDEs are compatible with fix-bug?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for fix-bug?

Requires knowledge of WordPress and Formidable Forms plugin ecosystems. Limited to bug-fixing workflows for these specific ecosystems.

How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add Strategy11/formidable-forms/fix-bug. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use fix-bug immediately in the current project.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

fix-bug

Install fix-bug, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

Fix Bug

Structured bug-fixing workflow for the Formidable Forms plugin ecosystem, following WordPress, Formidable Forms, and WordPress VIP coding standards.

This skill builds on the always-on rules in .windsurf/rules/enterprise/ which define core principles, code change phases, writing style, and commit message format. Those rules apply automatically to every conversation. This skill extends them with bug-fix-specific steps.

When to Use

  • Fixing reported bugs
  • Debugging unexpected behavior
  • Investigating error logs
  • Resolving compatibility issues

Coding Standards

Before writing or modifying ANY code, read and follow the applicable rules from .windsurf/rules/:

File typeRules to read
*.phpformidable/frm-php.md, wordpress/php.md, wordpress-vip/wpvip-security.md, wordpress-vip/wpvip-performance.md
*.js, *.jsx, *.mjsformidable/frm-javascript.md, wordpress/javascript.md, wordpress-vip/wpvip-security.md
*.css, *.scssformidable/frm-css.md
*.htmlwordpress/html.md
Block editor codewordpress/block-editor.md, wordpress-vip/wpvip-block-editor.md
UI/forms/user-facingwordpress/accessibility.md
Testsformidable/testing.md

How to apply:

  1. Before implementing, read ALL rules that match the file types you will modify
  2. Follow every rule when writing new code or modifying existing code

Workflow

The always-on rule enterprise/code-change-principles.md defines the core phases: Understand, Locate, Research, Select Solution, Implement, and Verify. The steps below are additional bug-fix-specific requirements.

Phase 4: Design

Phase 6: Verify

Phase 7: Report

Output a single concise report following report-template.md.

The report contains all deliverables:

markdown
1Report 2├── Root Cause → Fix (1 sentence each) 3├── Files Changed (file path + what changed) 4├── PR Info 5│ ├── Branch (fix/{issue}-{slug}) 6│ ├── PR Title (human-readable, NOT conventional commit format) 7│ ├── PR Body (Fixes URL + description + test steps) 8│ └── Commit Msg (conventional commit, NO issue number) 9└── Manual Test Steps (numbered reproduction/verification)

See pr-template.md for PR title, PR body, and commit message formatting rules.


Supporting Resources

Invocation

Cascade automatically invokes this skill when your request matches bug-fixing tasks.

To manually invoke:

text
1@fix-bug

Related Skills

Looking for an alternative to fix-bug or another community skill for your workflow? Explore these related open-source skills.

View All

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

333.8k
0
AI

widget-generator

Logo of f
f

Generate customizable widget plugins for the prompts.chat feed system

149.6k
0
AI

flags

Logo of vercel
vercel

The React Framework

138.4k
0
Browser

pr-review

Logo of pytorch
pytorch

Tensors and Dynamic neural networks in Python with strong GPU acceleration

98.6k
0
Developer