بنقرة واحدة
code-analysis
Check if code is readable by non-developers - clear names, plain English comments, no jargon
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Check if code is readable by non-developers - clear names, plain English comments, no jargon
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
A-share short-term trading decision skill for 1-5 day horizon. Use when you need real-data market sentiment, sector rotation, strong stock scanning, capital flow confirmation, date-based short-term signal scoring, prediction logging, and next-day market comparison for CN A-share momentum trading.
Generate agile release plans with sprints and roadmaps using unique sprint codes. Use when creating sprint schedules, product roadmaps, release planning, or when user mentions agile planning, sprints, roadmap, or release plans.
Change public APIs without breaking clients—versioning schemes, additive vs breaking changes, deprecation windows, and comms. Use when shipping breaking changes, sunsetting fields, or coordinating mobile/web SDK consumers.
Organizational coding standards and architectural patterns. References comprehensive skills for detailed patterns. Use when making architecture decisions or implementing features.
Search arXiv preprint repository for papers in physics, mathematics, computer science, quantitative biology, and related fields.
ATLAS Framework - Structured AI-assisted development methodology with GOTCHA 6-layer architecture and 5-step app building workflow. Use when building applications, creating workflows, or setting up agentic systems.
| name | code-analysis |
| description | Check if code is readable by non-developers - clear names, plain English comments, no jargon |
| version | 1.0.0 |
| author | abereyes |
| triggers | ["check readability","is this code clear","can non-devs understand"] |
Analyzes code to ensure non-developers (managers, stakeholders, new team members) can understand it.
python3 analyze.py --path your-file.py --strictness lenient
Bad Code (score: 71/100):
def proc(usr, tkn):
tmp = usr + tkn
return tmp * 2
Issues: Cryptic names, no comments, unclear purpose.
Good Code (score: 95/100):
def process_user_authentication(username, auth_token):
"""Validate user credentials and return auth score"""
combined_credential = username + auth_token
return combined_credential * 2
--strictness lenient to reduce noise