code-analysis
Check if code is readable by non-developers - clear names, plain English comments, no jargon
Installation
Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.
View source ↗GuidesSkill instructions
Code Readability Checker
Analyzes code to ensure non-developers (managers, stakeholders, new team members) can understand it.
What It Checks
- Clear naming: No cryptic abbreviations (usr_tkn → userToken)
- Plain comments: Everyday language, not technical jargon
- Documentation: What/Why/How for major sections
- Comment ratio: At least 20% of lines should be comments
Usage
python3 analyze.py --path your-file.py --strictness lenient
Example
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
Known Issues
- May flag false positives in documentation files
- Works best on actual production code
- Use
--strictness lenientto reduce noise
Examples
Read the usage examples in the source repository.
View source ↗Source history
- Indexed on
- 2026-01-20
- Index updated
- 2026-01-28
- Branch
- main
Index and sync dates describe this directory. View the source repository for code history.
GitHub ↗chat Comments (0)
Sign in to join the discussion and leave a comment.
No comments yet. Be the first to share your thoughts!