professor-triage

Analyze GitHub issues against the codebase and post prioritized triage comments.

13|6|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/baekenough/second-brain --skill professor-triage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: professor-triage
Source: https://github.com/baekenough/second-brain/tree/main/.claude/skills/professor-triage
Command: npx skills add https://github.com/baekenough/second-brain --skill professor-triage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes GitHub issues against the current codebase and performs automated triage with priority assessment to streamline backlog management and release planning.

Core Features & Use Cases

  • Automated cross-analysis of issues against the codebase to determine impact, blast radius, and actionability.
  • Automated triage actions, prioritized reports, and structured comments to guide maintainers.
  • Applicable to open-source or private repositories during issue triage, sprint planning, and code-review cycles.

Quick Start

Invoke /professor-triage with issue numbers or filters to start triaging issues against the current codebase.

Frequently Asked Questions about professor-triage

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

FAQPage Schema
How do I automate GitHub issue triage against my codebase?

You can automate GitHub issue triage by invoking the Skill with specific issue numbers or filters. It cross-analyzes issues against your codebase, extracts context, and posts structured comments with priority assignments directly to GitHub.

What is codebase-driven issue triage and how does it determine impact?

Codebase-driven issue triage evaluates GitHub issues by extracting codebase context and performing static analysis. It identifies the impact and blast radius of reported problems to determine actionability and assign accurate priority levels for release planning.

Can I use automated triage for private repositories and sprint planning?

Yes, automated triage works for both open-source and private repositories. It is specifically applicable during issue triage, sprint planning, and code-review cycles to streamline backlog management and guide maintainers with structured comments.

What's the best way to generate prioritized reports for GitHub issues?

The best way to generate prioritized reports for GitHub issues is using codebase context extraction and static analysis. This approach evaluates issue impact and blast radius, then outputs structured reports and automated comments to guide maintainers.

Does automated issue triage require external dependencies to analyze code?

No external dependencies are required to analyze code. The Skill operates independently using codebase context extraction, static analysis, and GitHub API automation to evaluate issues, determine impact, and post structured triage comments.