ReddRadar
Agent skill
perl-validate
This skill should be used when the user asks to "validate Perl script", "check Perl syntax", "verify Perl code", "/perl-validate", or mentions script validation, compile check, security review, or best practice compliance for Perl code.
Stars
33
Forks
4
Install this agent skill to your Project
npx add-skill https://github.com/Jamie-BitFlight/claude_skills/tree/main/plugins/perl-development/skills/perl-validate
SKILL.md
Perl Script Validation
Comprehensive validation of Perl scripts for syntax, security, and best practices.
Validation Checklist
- Syntax check (
perl -c) - Essential pragmas verification
- Security pattern review
- Best practice compliance
- Documentation check
Syntax Validation
Basic Compile Check
bash
# Check syntax
perl -c script.pl
# With warnings
perl -wc script.pl
# Check module
perl -c -I lib lib/MyApp/Module.pm
Expected Output
Success:
text
script.pl syntax OK
Failure:
text
syntax error at script.pl line 15, near "my $"
script.pl had compilation errors.
Essential Pragmas Check
Every production script MUST have:
perl
#!/usr/bin/env perl
use strict;
use warnings;
use autodie; # For scripts with file operations
Validation Pattern
bash
# Check for strict
grep -l 'use strict' script.pl || echo "MISSING: use strict"
# Check for warnings
grep -l 'use warnings' script.pl || echo "MISSING: use warnings"
# Check shebang
head -1 script.pl | grep -q '^#!' || echo "MISSING: shebang line"
Security Validation
Critical Checks
| Issue | Pattern to Find | Fix |
|---|---|---|
| Two-arg open | open\s+\w+,\s*[^<>] |
Use 3-arg open |
| Backticks with variables | `.*\$` |
Use IPC::System::Simple |
| eval with string | eval\s+" |
Use eval block |
| No taint mode | #!/.*perl\s*$ |
Add -T flag |
Security Check Commands
bash
# Find two-argument open
grep -n 'open\s\+[A-Z]\+\s*,' script.pl
# Find unsafe backticks
grep -n '`.*\$' script.pl
# Find string eval
grep -n 'eval\s*"' script.pl
# Check for system with string
grep -n 'system\s*"' script.pl
Best Practices Validation
Variable Declarations
bash
# Find undeclared variables (after perl -c passes)
# These would be caught by strict, but double-check:
grep -n '\$[a-z_][a-z0-9_]*\s*=' script.pl | head -20
Function Definitions
Check for proper function structure:
perl
# Good pattern
sub function_name {
my ($arg1, $arg2) = @_;
# ...
}
# Check for named parameters
grep -n 'sub.*{' script.pl
Error Handling
bash
# Find eval blocks without error check
grep -n 'eval\s*{' script.pl
# These should be followed by or do { } patterns
Documentation Validation
POD Check
bash
# Validate POD syntax
podchecker script.pl
# Check for POD presence
perl -MPod::Usage -e 'pod2usage(-input => shift)' script.pl >/dev/null 2>&1 || echo "No POD documentation"
Required POD Sections
bash
# Check for NAME section
grep -l '^=head1 NAME' script.pl || echo "MISSING: =head1 NAME"
# Check for SYNOPSIS
grep -l '^=head1 SYNOPSIS' script.pl || echo "MISSING: =head1 SYNOPSIS"
Comprehensive Validation Script
Run complete validation:
Quick Validation Commands
Syntax only:
bash
perl -wc script.pl
Pragmas check:
bash
head -10 script.pl | grep -E 'use (strict|warnings|autodie)'
Security scan:
bash
perlcritic --severity 5 script.pl
Full validation:
bash
perl -wc script.pl && \
grep -q 'use strict' script.pl && \
grep -q 'use warnings' script.pl && \
echo "Basic validation passed"
Fixing Common Issues
Missing strict/warnings
Add to top of script:
perl
use strict;
use warnings;
Two-argument open
perl
# Wrong
open FILE, $filename;
# Correct
open my $fh, '<', $filename;
Unsafe system calls
perl
# Wrong
system("rm $file");
`ls $dir`;
# Correct
use IPC::System::Simple qw(system capture);
system('rm', $file);
my $output = capture('ls', $dir);
Missing error handling
perl
# Wrong
open my $fh, '<', $file;
# Correct (with autodie)
use autodie;
open my $fh, '<', $file;
# Or explicit
open my $fh, '<', $file
or die "Cannot open $file: $!";
Didn't find tool you were looking for?