skills/compound-v-persist/SKILL.md
Resolves target repository and storage location for conversation artifacts. Guarantees organized, time-sorted history.
npx skillsauth add shermanhuman/compound-v compound-v-persistInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use this skill BEFORE writing any artifact to .promptherder/.
When multiple repositories are open in the workspace, all .promptherder/ paths target the repository the user is working in, not the methodology source repo. Infer the target from the user's active document or recent conversation context. If the active document is outside all repositories, use recent conversation context (which files were read/written). If still ambiguous, ask which repository before writing.
Install paths: promptherder writes agent files to .agents/ by default. Antigravity currently uses .agents/ and still reads the legacy .agent/ path for backward compatibility. Global skills live at ~/.gemini/antigravity/skills/. Workspace skills live at .agents/skills/, with legacy setups using .agent/skills/.
The "slug" is the folder name in .promptherder/convos/. It MUST follow the format:
YYYY-MM-DD-kebab-case-topic
Logic flow:
YYYY-MM-DD-, prepend today's date.plan.md?ideas.md (brainstorming)?
-> CREATE NEW: Generate a short, descriptive kebab-case slug based on the goal.review-*.md?debug.md?task.md?
-> REUSE LATEST: Find the most recently modified folder in .promptherder/convos/.
plan.md, treat as New Topic..promptherder/convos/<YYYY-MM-DD>-<slug>/Return the full absolute path for the file to be written (e.g., .../2024-01-01-fix-login/plan.md).
development
Mandatory checklist before claiming a task is done. Ensures verification, clean code, and accurate reporting. Use before saying "done" or "complete".
development
Applies tests-first discipline (red/green/refactor) and adds regression tests for bugs. Use when implementing features, fixing bugs, or refactoring.
testing
Reviews changes for correctness, edge cases, style, security, and maintainability with severity levels. 10 parallel checks with version-specific research. Use before finalizing changes.
research
Autonomous planning with internal reasoning. Researches, evaluates ideas, presents a plan. Minimizes user round-trips. Use before making non-trivial changes.