ronniegeraghty/history-hygiene
.squad/templates/skills/history-hygiene/SKILL.md
Record final outcomes to history.md, not intermediate requests or reversed decisions
$ install --global
skillsauthnpx skillsauth add ronniegeraghty/hyoka history-hygieneInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 30, 2026, 1:26 AM5.2s1 file scanned
SKILL.md
- name:
- history-hygiene
- description:
- Record final outcomes to history.md, not intermediate requests or reversed decisions
- domain:
- documentation, team-collaboration
- confidence:
- high
- source:
- earned (Kobayashi v0.6.0 incident, team intervention)
Context
History files (.md files tracking decisions, spawns, outcomes) are read cold by future agents. Stale or incorrect entries poison decision-making downstream. The Kobayashi incident proved this: history said "Brady decided v0.6.0" when Brady had reversed that to v0.8.17. Future spawns read the wrong truth and repeated the mistake.
Patterns
- Record the final outcome, not the initial request.
- Wait for confirmation before writing to history — don't log intermediate states.
- If a decision reverses, update the entry immediately — don't leave stale data.
- One read = one truth. A future agent should never need to cross-reference other files to understand what actually happened.
Examples
✓ Correct:
- "Migration target: v0.8.17 (initially discussed as v0.6.0, corrected by Brady)"
- "Reverted to Node 18 per Brady's explicit request on 2024-01-15"
✗ Incorrect:
- "Brady directed v0.6.0" (when later reversed)
- Recording what was requested instead of what actually happened
- Logging entries before outcome is confirmed
Anti-Patterns
- Writing intermediate or "for now" states to disk
- Attributing decisions without confirming final direction
- Treating history like a draft — history is the source of truth
- Assuming readers will cross-reference or verify; they won't
Related Skills
ronniegeraghty/sdk-version-check
development
VerifiedTrustedCommunity
Identifies Azure SDK packages in generated code and checks whether they are the latest available versions. Use during code review to catch outdated dependencies.
1SKILL.mdUpdated Apr 16, 2026
ronniegeraghty/reviewer-build
development
VerifiedTrustedCommunity
Sets up build environments for generated Azure SDK code samples and attempts to compile/build without modifying generated files. Use during review to verify code compiles correctly.
1SKILL.mdUpdated Apr 16, 2026
ronniegeraghty/skills/reviewer/java-sdk-validation
development
VerifiedTrustedCommunity
# Java SDK Validation Skill You are a **Java Azure SDK validation reviewer** for generated code samples. Your job is to check whether generated Java code follows modern Azure SDK for Java conventions and flag violations of common anti-patterns that LLMs frequently produce. ## Rules 1. **NEVER modify generated code.** You are evaluating, not fixing. 2. Report all findings honestly — pass or fail with specific evidence. 3. Check every rule below. A single violation in a category means that cate
1SKILL.mdUpdated Apr 16, 2026
ronniegeraghty/code-review-comments
development
VerifiedTrustedCommunity
Reads generated Azure SDK code files and adds inline review comments without changing any actual code. Use during code review to annotate quality issues, best practices, and suggestions.
1SKILL.mdUpdated Apr 16, 2026