Skip to content

DebugPilot AI — AI-Powered Debugging Workflow#156

Open
Yashyr190 wants to merge 1 commit into
Lamatic:mainfrom
Yashyr190:debugpilot-ai-submission
Open

DebugPilot AI — AI-Powered Debugging Workflow#156
Yashyr190 wants to merge 1 commit into
Lamatic:mainfrom
Yashyr190:debugpilot-ai-submission

Conversation

@Yashyr190
Copy link
Copy Markdown

@Yashyr190 Yashyr190 commented May 12, 2026

DebugPilot AI

DebugPilot AI is an AI-powered debugging workflow designed to help developers triage runtime errors, deployment failures, API issues, and stack traces more efficiently.

Instead of generic conversational responses, the system focuses on structured engineering workflows including:

  • severity classification
  • subsystem detection
  • root cause analysis
  • debugging checklists
  • prevention guidance
  • confidence scoring

🚀 Live Demo

https://debugpilot-ai.vercel.app/

📂 GitHub Repository

https://github.com/Yashyr190/debugpilot-ai

🎥 Demo Video

https://drive.google.com/file/d/1B6vfclYXRypmdNDDFDD16DtDiTtuYRL2/view?usp=sharing


Contribution Type

  • Challenge Submission
  • AgentKit Bundle
  • Production Template
  • SDK/Core Contribution

This PR is intended as a challenge showcase/workflow prototype rather than a production-ready AgentKit package.


Project Focus

The project focuses on:

  • AI-powered debugging workflows
  • structured incident triage
  • developer-focused UX
  • operational debugging outputs
  • practical AI workflow design

Validation Notes

  • Project tested locally and via deployed production build
  • Live deployment verified on Vercel
  • README documentation completed
  • Demo walkthrough included
  • No additional config.json or flows structure required for this showcase-style submission

Tech Stack

  • Next.js 14
  • TypeScript
  • Tailwind CSS

Features

  • AI-powered incident triage
  • Structured debugging workflows
  • Severity detection
  • Likely subsystem identification
  • Immediate next-step guidance
  • Confidence scoring
  • Modern developer-focused UI

Future Improvements

  • GitHub repository-aware debugging
  • CI/CD log ingestion
  • AI-generated PR fixes
  • Multi-agent debugging workflows

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 12, 2026

Walkthrough

This pull request adds a comprehensive README for the DebugPilot AI project. The documentation covers the problem statement, solution approach, core features, system architecture with LLM and fallback modes, tech stack, setup instructions, and future roadmap. No code changes are included.

Changes

DebugPilot AI Project Documentation

Layer / File(s) Summary
Complete README with features, architecture, and setup guide
submissions/debugpilot-ai
Documentation introduces DebugPilot AI as an AI-powered debugging assistant, explains the problem of unstructured incident workflows, and documents features including severity classification, subsystem identification, root cause analysis, checklists, and confidence scoring. Describes the Next.js architecture with optional LLM integration or local heuristic fallback, tech stack details, step-by-step setup instructions, optional OPENAI_API_KEY configuration, future improvements, project rationale, and MIT license.
🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Description check ❓ Inconclusive The PR description is non-standard for this repository template. It's a challenge submission rather than a kit/bundle/template following the repository's required structure. Clarify whether this challenge submission should follow the standard PR template requirements, or if challenge submissions use a different validation process outside the documented checklist structure.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly describes the main change—a README addition for DebugPilot AI, an AI-powered debugging workflow project submission.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

  • Generate code and open pull requests
  • Plan features and break down work
  • Investigate incidents and troubleshoot customer tickets together
  • Automate recurring tasks and respond to alerts with triggers
  • Summarize progress and report instantly

Built for teams:

  • Shared memory across your entire org—no repeating context
  • Per-thread sandboxes to safely plan and execute work
  • Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@Yashyr190
Copy link
Copy Markdown
Author

Hi maintainers

This PR was submitted for the agentkit-challenge.

I don’t appear to have permission to add labels from my side, so requesting the agentkit-challenge label to enable review automation.

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants