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

allcll-analysis

Analyze backend code and system behavior to identify root causes and risks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you investigate allcll-backend issues by first collecting evidence, understanding impact, and isolating likely causes before any fix is proposed.

Core Features & Use Cases

  • Root Cause Analysis: Trace errors, regressions, and unexpected behavior back to the most probable source.
  • Performance and Security Review: Inspect bottlenecks, risky patterns, and architecture or data-flow concerns in a read-only way.
  • PR-Style Defect Review: Evaluate code changes for correctness, blast radius, and operational impact before implementing follow-up work.
  • Use Case: When a backend feature is failing or slowing down, use this Skill to summarize findings, impacted components, and recommended next steps.

Quick Start

Ask the AI to analyze the relevant backend path or issue and return evidence-based findings with likely causes, impact, and recommended next actions.

Frequently Asked Questions about allcll-analysis

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

FAQPage Schema
How do I perform a root cause analysis on failing backend code?▼

Backend performance bottlenecks are inspected by analyzing system behavior and data flow in a read-only investigation, identifying risky patterns and summarizing impacted components and recommended next steps.

What is the best way to review backend code for security risks and defects?▼

Backend code review for security risks and defects evaluates code changes for correctness, blast radius, and operational impact using evidence-first reasoning that separates findings from later fixes or refactors.

Can I use evidence-first reasoning to diagnose backend issues without modifying the codebase?▼

Evidence-first reasoning applies to read-only investigations of backend repository architecture and data flow, ensuring findings are isolated from any subsequent fix, refactor, or test implementation.

Why does my backend feature slow down under specific data flow conditions?▼

Backend features slow down due to performance bottlenecks in data flow and architecture, which are diagnosed by inspecting system behavior, summarizing findings, and isolating likely causes before implementing fixes.

Are there limitations to diagnosing backend issues when the root cause is obscured by complex architecture?▼

Diagnosing backend issues with complex architecture requires tracing data flow and isolating probable causes, but evidence-first analysis is limited to read-only investigations and does not implement fixes or tests directly.

Related Skills

Explore More Software Engineering Skills→
JanuaryLabsJanuaryLabs
4

openspec-explore

Explore architecture and design options by reading repository files and OpenSpec artifacts without writing code.

Official
Intermediate
dakshrawat298-gifdakshrawat298-gif

security-fix-review

Review security patches for root-cause coverage and bypass risks.

Community
Intermediate
AreteDriverAreteDriver
4

cicd-pipeline

Implements CI/CD pipelines using Batcomputer for automated code review and deployment gating.

Community
Advanced
eliottbusinesseliottbusiness

requesting-code-review

Automate pre-commit code review with static analysis and security scanning.

Community
Advanced