Claudfather
Official@Claudfather
Rise of the machines. And really bad puns.
Agent Skills by Claudfather
Showing 38 vetted skills indexed across 1 GitHub repositories.
sync-branches
Fetches origin/main and merges it into all local branches and worktrees across sibling git repositories.
kindle
Discovers requirements and produces an approved spec before any implementation begins.
cleanup-legacy-install
Detects and removes legacy clauDNA overlay files from ~/.claude/ after plugin migration.
capture
Saves notes, external content, and session learnings to a Claudron knowledge vault.
product-enhance
Discover product enhancement opportunities through intent interviews and codebase gap analysis.
development-retro
Surfaces systemic patterns, friction points, and follow-up observations from a completed development session.
github-activity-report
Generates GitHub activity reports by crawling per-repo pulls and commits endpoints via the gh CLI.
vercel
Deploy, inspect logs, and check project status on Vercel via the CLI.
ironclad
Reviews GitHub plan issues and pull requests with a panel of parallel subagent lenses.
verify-completion
Validates completion claims by requiring fresh verification command output before reporting success.
heist
Extract reusable skills, config patterns, and approaches from any GitHub repository.
dbt
Runs dbt build, test, compile, and full-refresh commands against Snowflake.
using-claudna
Locate installed clauDNA skills by intent and run a six-check installation health diagnostic.
worktree
Creates git worktrees and orchestrates parallel subagents for concurrent feature development.
railway
Deploy services, inspect logs, and monitor project status on Railway via its CLI.
find-skills
Searches and installs agent skills from the open skills ecosystem using the npx skills CLI.
qa
Automates headless-browser QA testing, visual crawls, and performance benchmarking against running web applications.
adversarial-review
Stress-tests plans and proposals through pre-mortem analysis and seven structured critique lenses.
recall
Surfaces prior project decisions and fleet knowledge before starting repository work.
claudron
Search the shared knowledge vault and report vault health via the Claudron CLI.
publish
Publishes validated markdown documents to vaults, repos, GitHub issues, PRs, sessions, or Notion.
file-github-issue
Files structured GitHub issues from screenshots and descriptions using the gh CLI.
audit
Audits codebases through twelve concern lenses covering security, tech debt, design, data models, and scale.
forge
Generates structured multi-phase planning documents with decision forks for GitHub Issues or docs.
Frequently Asked Questions About Claudfather
FAQPage SchemaWhat tasks can I accomplish with Claudfather's clauDNA skills?▼
The suite covers the full development loop: ideation specs (kindle), multi-PR planning (forge), plan execution (build/build-all), PR review and hardening (review-work, ironclad), git worktree and branch sync, deployments to Vercel/Railway/Modal, Neon PostgreSQL branching, dbt-on-Snowflake runs, headless-browser QA, production incident investigation, and a shared knowledge vault (capture/recall/publish).
Who is the target user for these skills?▼
Software engineers and technical leads running Claude Code who manage multi-repo workspaces, parallel sessions via git worktrees, and multi-phase epics. It suits developers shipping PRs through GitHub, operating services on Vercel, Railway, or Modal, and teams wanting persistent cross-session knowledge through the Claudron vault.
How are the skills installed and invoked at runtime?▼
Skills install as a marketplace plugin, with cleanup-legacy-install removing stale pre-plugin ~/.claude overlays. Each user-invocable skill runs via slash commands like /claudna:ship or /claudna:qa with argument hints; using-claudna verifies installation health, versions, hooks, and loadable skills at session start.
What external dependencies do the skills require?▼
Dependencies are per-skill: gh (GitHub CLI) for PR and issue operations, vercel/railway/modal CLIs for deployments, psql plus neon CLI for database branching, dbt CLI for Snowflake models, claudron>=0.2 for vault capture/recall/lookup, and npx for discovering ecosystem skills. Several degrade gracefully when optional CLIs are absent.
How does the knowledge vault system work?▼
Capture writes notes, URLs, files, or session learnings to the vault with index-backed dedup via the Claudron CLI; recall surfaces prior decisions and conventions before starting work; claudron lookup searches by term; publish routes finished documents to the vault, docs tree, GitHub issues, PRs, or Notion. Without Claudron, skills fall back to INDEX.md scans.