skills.rest
allcll
allcllOFFICIAL
Explore all skills by this author →
WebsiteGitHub

allcll 코드 분석 가이드

Analyzes the allcll backend codebase for risks and bottlenecks without modifying files.

26|1|Updated Jan 8, 2025
Search Tags:#code analysis#root cause analysis#security review#sse#performance review#scheduler#architecture mapping
One-click install
npx skills add https://github.com/allcll/allcll-backend --skill allcll
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: allcll 코드 분석 가이드
Source: https://github.com/allcll/allcll-backend/tree/main/docs/agent-harness/skills/analysis
Command: npx skills add https://github.com/allcll/allcll-backend --skill allcll

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you analyze the allcll backend safely and systematically when you need root-cause analysis, architecture mapping, performance review, or security review without making changes.

Core Features & Use Cases

  • Read-only analysis: Inspect code paths, identify failure scenarios, and report findings without modifying production, test, or documentation files.
  • Architecture and flow mapping: Trace responsibilities across domain, admin, client, support, and config packages to understand data flow and change impact.
  • Performance and RCA review: Evaluate SSE, scheduler, batch, storage, and external API paths for bottlenecks, races, and operational risks.
  • Security review: Assess secret exposure paths, token handling, and logging risks while avoiding sensitive file contents.
  • Use Case: A developer asks why SSE seat pushes are delayed at peak time, and this Skill maps the hot path, likely bottlenecks, and the metrics needed to confirm them.

Quick Start

Ask me to analyze the allcll backend flow you care about, and I will summarize findings, risks, and follow-up checks without changing any files.

Frequently Asked Questions about allcll 코드 분석 가이드

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

FAQPage Schema
How do I find the root cause of delayed SSE seat pushes without modifying backend code?▼

Root cause analysis for delayed SSE seat pushes requires read-only inspection of hot paths, scheduler bottlenecks, and package boundaries to identify likely performance issues and operational risks without modifying production files.

What is the best way to map architecture boundaries for a backend codebase safely?▼

Architecture mapping traces responsibilities across domain, admin, client, support, and config packages to understand data flow and change impact, ensuring systematic and safe analysis without altering test or production environments.

How do I perform a security review to assess secret exposure paths and token handling risks?▼

Security review assesses secret exposure paths, token handling, and logging risks by carefully gathering evidence from code paths and non-sensitive configuration names while avoiding sensitive file contents during the inspection process.

Can I analyze scheduler and storage performance bottlenecks for a backend system in read-only mode?▼

Yes, read-only analysis evaluates scheduler, SSE, batch, seat storage, and external API paths to identify performance bottlenecks, races, and operational risks by inspecting code paths without changing any production or test files.

What are the limitations of read-only code analysis for identifying failure scenarios?▼

Read-only code analysis limitations include the inability to directly fix identified root causes or bottlenecks, requiring follow-up checks and metrics gathering to confirm findings before implementing actual code modifications.

When do I need architecture and flow mapping to support debugging scenarios?▼

Architecture and flow mapping is needed for review-style debugging scenarios when tracing data flow, evaluating graduation policy or admin ingestion logic, and understanding change impact across package boundaries to support evidence gathering.

Related Skills

Explore More Software Engineering Skills→
PicoMLXPicoMLX

bug-hunt-swarm

Coordinate parallel read-only sub-agents to diagnose software bugs and rank root causes.

Official
Advanced
sumeetonline90sumeetonline90

security-scan

Scan Claude Code configuration directories for security vulnerabilities and misconfigurations.

Community
Intermediate
ryanmatryanmat

lm-apm

Investigate LogicMonitor APM trace data to diagnose service issues and correlate alerts.

Community
Advanced
kynoptickynoptic
1

Debugging Runtime Errors

Analyze stack traces and error logs to identify root causes and propose fixes.

Community
Advanced