specstory-guard
Install a pre-commit hook that scans .specstory/history for secrets before commits. Run when user says "set up secret scanning", "install specstory guard", "protect my history", or "check for secrets".
89
88%
Does it follow best practices?
Impact
88%
1.06xAverage score across 3 eval scenarios
Passed
No known issues
Evaluation results
100%
Set Up Commit Protection for AI Session History
Guard installation workflow
Uses guard.py install
100%
100%
No manual hook writing
100%
100%
Install command recorded
100%
100%
Hook location confirmed
100%
100%
Skills directory placement
100%
100%
Scanned directory explained
100%
100%
Auto-trigger on commit
100%
100%
Hook contains guard marker
100%
100%
No external dependencies
100%
100%
Guard purpose explained
100%
100%
96%
8%Pre-Push Security Audit of AI Session History
Scan findings presentation
Uses guard.py scan
100%
100%
Scans .specstory/history/
100%
100%
File names in report
100%
100%
Line numbers in report
100%
100%
Rule names in report
100%
100%
Redacted snippets only
100%
100%
Offer to redact
0%
66%
Finding count reported
100%
100%
Multiple files covered
100%
100%
Secret types identified
100%
100%
70%
8%Clean Up SpecStory History Before Open-Sourcing the Repository
Allowlist false positives and remediate real secrets
Uses SPECSTORY_GUARD_ALLOWLIST
0%
13%
Regex patterns in allowlist
50%
100%
Comma-separated allowlist format
0%
0%
Replaces secrets with [REDACTED]
75%
100%
Actual file modified
100%
100%
Re-scans after remediation
100%
83%
Clean scan confirmed
100%
100%
Distinguishes false positives
100%
100%
Uses guard.py for all scans
37%
25%
Commands documented
66%
66%
- Repository
- specstoryai/agent-skills
- Commit
9454d3f
- Evaluated
- Agent
- Claude Code
- Model
- Claude Sonnet 4.6
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.