WordPress.org
Get WordPress

Make WordPress Core

Opened 4 weeks ago

Last modified 9 days ago

#64749 new enhancement

Proposal: AI Pathfinding Assistant for WordPress Contributors

Reported by: marc4's profile Marc4 Owned by:
Milestone: Awaiting Review Priority: normal
Severity: normal Version:
Component: AI Keywords:
Focuses: Cc:

Description

I propose the creation of an AI-powered tool integrated into the WordPress ecosystem (Trac/GitHub) to act as a navigator for contributors. The goal is to remove the "entry barrier" of locating specific files or triage components within the massive WordPress codebase, saving countless hours of manual review and repetitive administrative tasks.

1. The Problem: The "Repository Wall"

For the majority of people who are unfamiliar with the intricate structure of WordPress repositories, contributing presents a logistical challenge before a technical one:

  1. Code Vastness: Locating where a specific function or style resides among thousands of files is daunting.
  1. Triage Burden: Maintainers spend valuable time moving tickets to the correct component or redirecting Pull Requests (PRs) submitted to the wrong repository.
  1. Contributor Friction: The fear of "doing it wrong" or the frustration of searching unsuccessfully for the right file actively discourages new contributions.

2. The Solution: AI Locator & Component Suggester

Implementing a Natural Language Interface (LLM) trained on the WordPress repository structure in GitHub and the Trac component hierarchy.

Primary Use Cases:

  1. File Localization:

User: "I've found a styling issue with the 'Publish' button in the editor."

AI Response: "That file is located at wp-admin/js/editor.js within the WordPress/gutenberg repository."

  1. Component Suggestion:

User: "I found a bug in how images are displayed in the theme gallery."

AI Response: "You should open this ticket under the 'Media' or 'Themes' component."

3. Key Benefits

  1. Team Efficiency: Dramatically reduces the time spent manually triaging and moving tickets.
  1. Democratizing Contribution: Empowers non-technical profiles—or developers unfamiliar with the vast file structure—to find exactly where to propose changes or suggestions.
  1. Accelerated "Time-to-PR": The transition from an idea to the first commit becomes nearly instantaneous.

Change History (1)

#1 @JeffPaul
9 days ago

Perhaps this should move to ​Meta Trac?

Note: See TracTickets for help on using tickets.