Results for “repository”

Generates a comprehensive AGENTS.md file at the repository root to provide AI coding agents with project context, setup commands, development workflows, testing instructions, and code style guidelines.

Generates a structured Claude CLI prompt from a JSON idea specification to bootstrap a complete skill directory with SKILL.md, references, scripts, and tests following repository conventions.

Publishes agent skills to GitHub with automatic validation of SKILL.md, README quality checks, repository creation or updates, and real installation verification via npx skills.

Scans repositories for markdown and HTML documentation, classifies files as repo-local or centralizable content, generates an inventory report, and optionally consolidates content into a centralized docs repository.

Creates clean conventional git commits using standard git and pushes changes to the remote repository. Use when the user asks to "commit and push", "push changes", or complete a commit followed by git push.

Colab notebook setup pattern. Trigger when: (1) Creating new Colab notebooks, (2) API key file not found, (3) file path errors in Colab, (4) repository extraction fails, (5) 'yfinance fallback' despite keys existing.

Provides backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes.

Use when you need a deterministic inspection of a WordPress repository (plugin/theme/block theme/WP core/Gutenberg/full site) including tooling/tests/version hints, and a structured JSON report to guide workflows and guardrails.

Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.

Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.

Extract actionable patterns, architecture decisions, code conventions, and skill-relevant insights from GitHub/GitLab repositories. Assess repo credibility, run the full security scan pipeline, and apply findings to existing skills, new skills, or the current project. Load when the user asks to learn from a repo, extract patterns from a codebase, study a repository, or analyze a repo for reusable techniques. Also triggers on "learn from this repo", "learn from this repository", "what can we learn from this codebase", "extract patterns from this repo", "study this repo".

Analyze a repository to generate recommended Claude Code settings.json permissions for read-only commands, detecting tech stack, build tools, and monorepo structure.

Extracts a language-agnostic ghost package (spec, tests, install and verify docs) from an existing repository, preserving behavior via tests.yaml and evidence bundles.

Builds an evidence-backed ECC install plan for a repository by sorting skills, commands, rules, hooks, and extras into DAILY vs LIBRARY buckets using parallel repo-aware review passes.

Interact with Gitea repositories, issues, pull requests, releases, and more via the gitea-mcp server or the tea CLI, with automatic detection of Gitea remotes.

Backs up the live global Claude Code configuration (settings.json, CLAUDE.md, statusline.ts) into a git repository, with an allowlist and secret scan to prevent leaking credentials.

Summarize each day's Git activity into a concise daily work log, for a single date or a range. Uses the current repository, optional configured work projects, or paths named in conversation; configuration is never required.

Use this when a Python service, package, or repository needs a maintainable internal structure for modules, domain logic, adapters, config, entrypoints, and tests. Trigger on requests about project layout and internal organization for Python systems.

Adds a new API connector or provider to a repository by matching its existing integration pattern exactly, including layout, config, auth, error handling, tests, and wiring.

Builds, refines, tests, or validates a CLI-Anything harness for a GUI application or source repository, producing a stateful Click CLI with JSON output and REPL mode.

Manage GitHub repositories end-to-end: clone, create, fork, configure settings, protect branches, set secrets, create releases, and run workflows using gh or git+curl.

Use when creating a note, document, script or project that shouldn't outlive a known date — interview prep, a migration, a course, a time-boxed experiment — so it gets deleted on time instead of rotting in the repository.

Creates a new AEM Edge Delivery site from scratch, including GitHub repository setup, aem-code-sync installation, initial content creation in DA, and preview URL generation.

Submits or updates a Wall of Apps entry in the App-Store-Connect-CLI repository using the `asc apps wall submit` command, with dry-run preview and confirmation.

Analyze repositories for lines of code, language breakdown, file counts, and code-vs-comment ratios using pygount, with guidance on using language servers for symbol navigation.

Show active or recent Claude Code jobs in this repository, or detailed status for a specific job id. Args: [job-id], --wait, --timeout-ms <ms>, --poll-interval-ms <ms>, --all. Use for tracked-job inspection, not setup or result retrieval.

Index and search code repositories, documentation, research papers, HuggingFace datasets, local folders, and packages via the Nia API, with AI-powered research and code advisor capabilities.

Builds an evidence-backed ECC install plan for a repository by sorting skills, commands, rules, hooks, and extras into DAILY vs LIBRARY buckets using parallel repo-aware review passes.

Provides idiomatic C# and .NET patterns covering immutability, dependency injection, async/await, options, result, repository, middleware, and minimal API conventions for building maintainable applications.

Use to build PNAS's Data Availability Statement and deposition plan — mandatory deposition of data in an approved repository at submission, accession numbers/DOIs, public + archived code, and materials sharing. "Available on request" is not sufficient for primary data.

Answer repository questions grounded entirely in source code evidence. Use when user asks a question about the codebase, user wants to understand a specific file, function, or component, or user asks "how does X work" or "where is Y defined".

Answer repository questions grounded entirely in source code evidence. Use when user asks a question about the codebase, user wants to understand a specific file, function, or component, or user asks "how does X work" or "where is Y defined".

Align a technical document with the actual code implementation and correct drift. Use when a user asks to update docs to match current behavior, audit a technical document against the repository, or fix stale architecture, API, workflow, or operator documentation.

Answer repository questions grounded entirely in source code evidence. Use when user asks a question about the codebase, user wants to understand a specific file, function, or component, or user asks "how does X work" or "where is Y defined".

Answer repository questions grounded entirely in source code evidence. Use when user asks a question about the codebase, user wants to understand a specific file, function, or component, or user asks "how does X work" or "where is Y defined".

Answer repository questions grounded entirely in source code evidence. Use when user asks a question about the codebase, user wants to understand a specific file, function, or component, or user asks "how does X work" or "where is Y defined".