skills.rest
ioku24
ioku24COMMUNITY
Explore all skills by this author →
WebsiteGitHub

identify

Identify friction points, bottlenecks, bugs, and technical debt across a codebase.

Updated Aug 23, 2026
Search Tags:#debugging#bottlenecks#friction#code-health#audits#identify
One-click install
npx skills add https://github.com/ioku24/autorankr --skill identify
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: identify
Source: https://github.com/ioku24/autorankr/tree/main/.claude/skills/5-system-framework/2.identify
Command: npx skills add https://github.com/ioku24/autorankr --skill identify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams surface friction, bottlenecks, bugs, and technical debt across a project. It enables proactive auditing, debugging, and pre-work analysis to surface hidden issues before they escalate.

Core Features & Use Cases

  • Comprehensive detection across Code Health, Performance, UX Friction, Architecture Debt, and Operational Gaps.
  • Supports audits, debugging sessions, and pre-work reviews to guide focused improvements.
  • Use Case: run an early system health check on a legacy module to surface critical issues and prioritize fixes.

Quick Start

Example: run a quick audit on the current project by identifying a target scope (module or system), performing a basic health check, and logging the findings to your centralized issues registry for triage.

Frequently Asked Questions about identify

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

FAQPage Schema
How do I identify technical debt and friction points across a codebase?▼

To identify technical debt and friction points, run a structured audit that checks code health, performance bottlenecks, UX friction, architecture debt, and operational gaps. It logs findings with clear severity levels into an actionable issues registry for triage.

What is a code health audit and when do I need to run one?▼

A code health audit is a proactive review to detect bugs, bottlenecks, and technical debt before they escalate. You need to run one during debugging sessions, before major system redesigns, or as an early health check on legacy modules.

How do I find performance bottlenecks before a major system redesign?▼

Finding performance bottlenecks before a system redesign requires a pre-work analysis on the target module scope. This process evaluates performance and architecture debt, logging actionable findings with severity levels to guide focused fixes.

Can I run a debugging session to surface architecture debt in a legacy module?▼

Yes, you can run a debugging session or early system health check on a legacy module to surface architecture debt. The process guides teams through detection categories and logs findings to an issues registry for prioritized improvements.

What is the best way to prioritize technical debt findings from a codebase audit?▼

The best way to prioritize technical debt findings is to use a structured logging system that assigns clear severity levels to each issue. This creates an actionable issues registry that drives focused fixes during triage and module-level reviews.

Related Skills

Explore More Software Engineering Skills→
Nickalus12Nickalus12
2

perf-check

Identify performance hotspots and regressions in Loom-style codebases.

Community
Intermediate
htafollahtafolla
5

bug-triage

Automate bug triage, root cause analysis, and issue prioritization for software development.

Community
Intermediate
global-osglobal-os

plugin-audit

Analyze Claude Code logs to audit Vercel-plugin performance and cache staleness.

Official
Advanced
KrismithReddy12KrismithReddy12

health

Calculate a weighted 0-10 code quality score from linters and test runners.

Community
Advanced