SAS
Execute these commands after EVERY implementation (see AGENT_AUTOMATION module for full workflow).
11 stars
byhivellm
Best use case
SAS is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Execute these commands after EVERY implementation (see AGENT_AUTOMATION module for full workflow).
Teams using SAS should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
$curl -o ~/.claude/skills/sas/SKILL.md --create-dirs "https://raw.githubusercontent.com/hivellm/rulebook/main/templates/skills/languages/sas/SKILL.md"
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/sas/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How SAS Compares
| Feature / Agent | SAS | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Execute these commands after EVERY implementation (see AGENT_AUTOMATION module for full workflow).
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
<!-- SAS:START -->
# SAS Project Rules
## Agent Automation Commands
**CRITICAL**: Execute these commands after EVERY implementation (see AGENT_AUTOMATION module for full workflow).
```bash
# Complete quality check sequence:
# Run SAS code validation (project-specific)
# Run SASUnit tests
# Check log files for errors/warnings
# SAS projects typically use:
sas -sysin validate_code.sas # Code validation
sas -sysin run_tests.sas # Run SASUnit tests
```
## SAS Configuration
**CRITICAL**: Use SAS 9.4+ with code validation and testing.
- **Version**: SAS 9.4+ or Viya 3.5+
- **Linter**: SAS Code Analyzer
- **Testing**: SASUnit or custom test frameworks
- **Version Control**: Track all .sas files
## Code Quality Standards
### Mandatory Quality Checks
**IMPORTANT**: These commands MUST match your GitHub Actions workflows!
```bash
# Pre-Commit Checklist (MUST match .github/workflows/*.yml)
# 1. Validate SAS code syntax (matches workflow)
sas -sysin your_program.sas -nosplash -print /dev/null
# 2. Run SASUnit tests (matches workflow)
%include "sasunit/run_all_tests.sas";
# 3. Check for warnings and errors (matches workflow)
grep -i "ERROR\|WARNING" your_program.log
# If ANY fails: ❌ DO NOT COMMIT - Fix first!
```
**Why This Matters:**
- SAS code with syntax errors will fail in production
- Missing test validation = data processing errors
### Code Style
```sas
/* Good: Clear, commented, structured */
%macro process_data(input_ds=, output_ds=, threshold=0.5);
%* Validate inputs;
%if %length(&input_ds) = 0 %then %do;
%put ERROR: input_ds parameter required;
%return;
%end;
/* Process data */
data &output_ds;
set &input_ds;
where value > &threshold;
run;
%mend;
```
<!-- SAS:END -->Related Skills
We are still matching the closest adjacent skills for this page. In the meantime, continue through the full directory.