julia-ci-buildkite
Configure Buildkite CI for Julia packages, especially for GPU testing and specialized hardware. Use this skill when setting up Buildkite pipelines.
Discover databases automation tools skills, compare source repositories and read the instructions for each workflow.
Configure Buildkite CI for Julia packages, especially for GPU testing and specialized hardware. Use this skill when setting up Buildkite pipelines.
Configure GitHub Actions CI for Julia packages including testing, documentation, and benchmarks. Use this skill when setting up or modifying CI workflows.
Create new Julia packages with modern infrastructure including tests, documentation, and CI. Use this skill when starting a new Julia package from scratch.
Use Git and the GitHub CLI for version control and pull request workflows in Julia package development. Use this skill when working with Git remotes, branches, and PRs.
Compile the YAML artifact into PROMPT.md with deterministic structure. A final agent pass polishes for fluidity, conciseness, and correctness.
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include website...
GitHub-first workflow - Issues, PRs, milestones, auto-tracking for solo developer productivity. Includes PR description templates, issue templates, automation patterns, and webhook security.
Documentation standards and automation. Use when updating docs, writing guides, or synchronizing code with documentation.
Detects stale documentation - outdated status markers, old TODOs, version lag
GenAI-powered semantic validation - detects outdated docs, version mismatches, and architectural drift
Enforces project file organization standards from CLAUDE.md/PROJECT.md - auto-fix mode
Documentation consistency enforcement - prevents drift between README.md and actual codebase state. Auto-activates when updating docs, committing changes, or working with skills/agents/commands.
Git best practices, commit conventions, branching strategies, and pull request workflows. Use when working with git operations, commits, branches, or PRs.
AI-powered validation of knowledge notes against current codebase. Detects stale content by comparing documented knowledge with actual files.
Use this skill when modifying, refactoring, or optimizing code. Enforces strict engineering standards and project-specific constraints.
Independent code auditor. Verifies code against a change log without prior context.
Use this skill for all version control tasks, including committing, branching, pushing, and reviewing history.
Intelligent agent for validating ERPNext/Frappe code against best practices and common pitfalls. Use when reviewing generated code, checking for errors before deployment, or validating code quality. Triggers: r...
This skill should be used when the user asks to "use Git in a task", "manage virtual environments", "use Docker Compose", "clone a repository", "create a venv", "run docker-compose", "use angreal.integrations",...
This skill should be used when the user asks to "create an angreal template", "make a project template", "build a reusable template", "share a template", "write angreal.toml", "use Tera templating", "template v...
Create GitHub issues with duplicate detection and codebase analysis. Use when you discover a bug, improvement, or issue that wasn't in the original scope/spec during development. Triggers on phrases like "creat...
Thoroughly analyze and understand the current codebase to enable effective work on any task. Use when starting work in an unfamiliar repo.
Publish files or Obsidian notes as GitHub Gists. Use when user wants to share code/notes publicly, create quick shareable snippets, or publish markdown to GitHub. Triggers include "publish as gist", "create gis...
Detects changes between joblib versions by comparing git diffs, analyzes API changes (new/modified/removed functions, classes, parameters), and updates corresponding .pyi stub files. Use when joblib releases a...
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.