Loading...
Loading...
Found 13 Skills
Guide for understanding and contributing to the awesome-game-security curated resource list. Use this skill when adding new resources, organizing categories, understanding project structure, or maintaining the README.md format consistency.
Add a new skill to the LaunchDarkly agent-skills repo. Use when creating a new SKILL.md, adding a skill to the catalog, or aligning with repo conventions. Guides exploration of existing skills before creating.
Repository management strategies including branch strategies (Git Flow, GitHub Flow, trunk-based), monorepo patterns, submodules, and repository organization. Use when user needs guidance on repository structure or branching strategies.
Turn raw PM content into a compliant, publish-ready skill by choosing build/add paths, running conformance checks, and updating docs before commit.
Development workflows for the playwright-cli repository. Use when the user asks about rolling dependencies, releasing, or other repo maintenance tasks.
Build or update the code review knowledge graph. Run this first to initialize, or let hooks keep it updated automatically.
This skill should be used when a new ArcKit command has been added and documentation needs updating across the repository. Triggers: update documentation for new command, update command count, add command to README, update DEPENDENCY-MATRIX, update docs/index.html, new command documentation checklist, update all docs for new command, add command to dependency matrix, update command tables, sync documentation after adding command, I added a new command what do I update, post-command documentation, new slash command docs.
Close a PRD that is already implemented or no longer needed
Clean up a Git repository's merged branches and worktrees, then prune filesystem cruft (recursively-empty directories and orphaned node_modules). Use when asked to clean up / tidy / prune merged branches, remove stale or finished worktrees, delete branches whose PRs have already merged (including squash-merges), or sweep empty directories and leftover node_modules. Two-pass merge detection (git ancestry plus merged GitHub PRs), an uncommitted-changes guard on worktrees, an optional Linear "Done" writeback, per-pass confirmation gates, and a --dry-run preview. Protected branches are never touched.
Contribute changes to the Feynman repository itself. Use when the task is to add features, fix bugs, update prompts or skills, change install or release behavior, improve docs, or prepare a focused PR against this repo.
Distills a completed deep-plan document (e.g. docs/PLAN.md) into durable project knowledge files: AGENTS.md (agent operating rules and verified ground truth), docs/ARCHITECTURE.md (component map, data flow, framework mechanisms with citations), and ROADMAP.md (phased roadmap with live status). Carries only VERIFIED evidence forward, re-checks stale claims, and merges into existing files instead of overwriting. Use after a deep-plan finishes, when the user mentions deep-plan-ingest or ingest the plan, or asks to generate/update AGENTS.md, ARCHITECTURE.md, or ROADMAP.md from a plan.
Use when creating, repairing, refactoring, validating, or documenting an academic research repository structure, including wiki, sources, SOTA, outputs, agent docs, tests, and reproducibility folders.