How does the skill handle critical security findings?

If a deferred finding is critical, the skill can apply an 'awaiting-dependencies' label to the parent issue, documenting a deviation that blocks progress until the dependency is resolved.

Does this skill require specific tools to be installed?

Yes, it requires the GitHub MCP (Model Context Protocol) and the GitHub CLI (gh) to be configured in your environment to create and manage issues.

What is 'Depth Tracking' in this context?

Depth tracking monitors how many levels deep a finding is. If a finding is discovered during the fix of a previous finding, the depth increments, helping teams identify deep-seated systemic issues.

Why use this skill instead of just commenting on a pull request?

Comments are often lost or forgotten once a PR is merged. This skill creates a formal, trackable GitHub issue to ensure the work is prioritized and completed in a future cycle.

Deferred Finding Manager

Name: Deferred Finding Manager
Author: troykelly

bytroykelly

•

Collaboration Tools

Automates the creation and tracking of GitHub issues for code review findings that cannot be addressed in the current pull request.

About

The Deferred Finding skill ensures that no code review observation is lost by formalizing the process of deferring work. It enforces technical debt management by requiring every deferred finding to be documented as a linked GitHub issue with full context, including severity, code location, and justification. By automating the creation of these tracking issues via the GitHub CLI, it prevents critical improvements from being forgotten and maintains a clear audit trail between parent pull requests and their subsequent follow-up tasks.

Key Features

Workflow integration for blocking dependencies on critical findings
Automated tracking issue creation with standardized templates
Severity-based labeling and review criteria categorization
Nested depth tracking to identify systemic architectural debt
5 GitHub stars
Automatic bidirectional linking between parent PRs and deferred issues

Use Cases

Managing out-of-scope architectural improvements discovered during feature development
Tracking non-critical security findings that require infrastructure-level changes
Organizing technical debt items identified during comprehensive code audits

About

Key Features

Workflow integration for blocking dependencies on critical findings
Automated tracking issue creation with standardized templates
Severity-based labeling and review criteria categorization
Nested depth tracking to identify systemic architectural debt
5 GitHub stars
Automatic bidirectional linking between parent PRs and deferred issues

Use Cases

Managing out-of-scope architectural improvements discovered during feature development
Tracking non-critical security findings that require infrastructure-level changes
Organizing technical debt items identified during comprehensive code audits