TheCardGoat/.agents/skills/memory-bank
.agents/skills/memory-bank/SKILL.md
--- name: memory-bank description: Manage Memory Bank development logs in .ai_memory/. Use when starting a new feature, updating progress on current work, adding implementation log entries, or checking log status. Triggers on: (1) Starting new features/tasks, (2) "update memory bank" or "log progress", (3) Adding dated entries to implementation logs, (4) Checking Memory Bank status. Always prepends entries with YYYY-MM-DD dates, newest first. --- # Memory Bank Manage development logs in `.ai_m
$ install --global
skillsauthnpx skillsauth add TheCardGoat/lorcana-engine .agents/skills/memory-bankInstall 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 17, 2026, 2:10 AM8.3s1 file scanned
SKILL.md
- name:
- memory-bank
- description:
- Manage Memory Bank development logs in .ai_memory/. Use when starting a new feature, updating progress on current work, adding implementation log entries, or checking log status. Triggers on: (1) Starting new features/tasks, (2) "update memory bank" or "log progress", (3) Adding dated entries to implementation logs, (4) Checking Memory Bank status. Always prepends entries with YYYY-MM-DD dates, newest first.
Memory Bank
Manage development logs in .ai_memory/ with chronological date ordering.
Date Ordering Rule
All entries use YYYY-MM-DD format. Newer entries appear FIRST (top of section).
This ensures recent context takes precedence when reading logs.
Operations
1. Create New Log
When starting a new feature/task:
# Get current branch
BRANCH=$(git rev-parse --abbrev-ref HEAD 2>/dev/null || echo "unknown")
DATE=$(date +%Y-%m-%d)
- Check if log exists:
ls .ai_memory/ - Copy template:
.ai_memory/TEMPLATE.md→.ai_memory/<branch-name>.md - Fill Context section with current date and branch
- Complete Problem Statement
2. Update Existing Log
When adding progress to an existing log:
- Read current log
- Identify section to update (Research, Proposed Solution, Status)
- Add content while preserving structure
3. Add Implementation Entry
Add dated entries to the Implementation Log section. Always prepend (newest first):
## Implementation Log
### 2025-12-29 ← NEW (add here)
- [x] Completed task A
- [ ] Started task B
### 2025-12-28 ← OLDER (stays below)
- [x] Initial setup
Process:
- Get today's date:
date +%Y-%m-%d - Check if today's entry exists
- If exists: Add items to existing date section
- If not: Create new date header at TOP of Implementation Log
4. Show Status
Report current Memory Bank state:
Memory Bank Status
==================
File: .ai_memory/<name>.md
Last Updated: YYYY-MM-DD
Sections:
- [x] Context (complete)
- [x] Problem Statement (complete)
- [ ] Research (incomplete)
- [ ] Proposed Solution (incomplete)
Implementation Progress:
- 3 entries logged
- Latest: YYYY-MM-DD
Quick Reference
| Action | Command Pattern | | --------- | ----------------------------------------- | | Create | Copy TEMPLATE.md, fill Context | | Update | Read → Modify section → Write | | Add Entry | Prepend dated entry to Implementation Log | | Status | List sections, check completion |
File Structure
.ai_memory/
├── README.md # Documentation
├── TEMPLATE.md # Copy for new logs
└── <branch>.md # Active development logs
Completion Report
After any operation, report:
Memory Bank: <operation>
========================
File: .ai_memory/<name>.md
Date: YYYY-MM-DD
Changes:
- <what was added/modified>
Next Steps:
- <suggested actions>
Related Skills
TheCardGoat/teach-impeccable
documentation
VerifiedTrustedCommunity
One-time setup that gathers design context for your project and saves it to your AI config file. Run once to establish persistent design guidelines.
12SKILL.mdUpdated Apr 17, 2026
TheCardGoat/skill-creator
tools
VerifiedTrustedCommunity
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
12SKILL.mdUpdated Apr 17, 2026
TheCardGoat/.agents/skills/review-pr-comments
development
VerifiedTrustedCommunity
--- name: review-pr-comments description: Systematically process GitHub pull request review feedback end-to-end: pick a target PR, identify unanswered or unresolved comments, handle each thread sequentially, implement required code updates, run repository verification checks, and post clear responses. Use when asked to review PR comments, resolve review threads, or address reviewer suggestions/questions. --- # Review PR Comments Process pull request feedback one thread at a time and finish wit
12SKILL.mdUpdated Apr 17, 2026
TheCardGoat/quieter
testing
VerifiedTrustedCommunity
Tone down overly bold or visually aggressive designs. Reduces intensity while maintaining design quality and impact.
12SKILL.mdUpdated Apr 17, 2026