feature-poc-finder

Identify feature owners by aggregating contributor signals from GitHub code and PR history, DevRev tickets, and Slack conversations. Provide a feature description, and the skill surfaces likely owners and collaborators across these integrated platforms.

Yes, you can find contributors for a specific module before raising a PR by querying with a feature description. The skill aggregates historical code commits, pull requests, and DevRev ticket assignments to pinpoint who has worked on the system.

If a source like Slack or DevRev MCP is not configured, the skill gracefully degrades. It proceeds with remaining available sources, such as GitHub, and explicitly informs you which integrations were skipped during the owner identification process.

Cross-source ownership identification works for debugging by pulling historical signals from GitHub commits, DevRev tickets, and Slack conversations. It aggregates these data points to highlight the developers most familiar with the feature, helping you contact the right collaborators.

No, you do not need all three sources to identify collaborators. The skill gracefully handles partially configured sources, meaning it can successfully surface likely owners using whatever subset of GitHub, DevRev, or Slack integrations you have active.

The best way to find who worked on a feature for code review is to query the skill with a feature description. It cross-references GitHub PR history, DevRev tickets, and Slack conversations to surface top contributors and assignees for the module.