「github」の検索結果

Research and stress-test open-source project names, from collision checks to launch-ready decisions. Use when the user asks to name or rename a project, compare candidate names, screen GitHub or package namespace risk, verify language or mythology claims, or improve SEO/GEO clarity. Perform live web and registry research, separate brand from category descriptor, classify collisions, and return one evidence-backed recommendation.

日本語の概要は準備中です。原文の説明を表示しています。

Package an AI skill, prompt workflow, or internal operating habit into a public-ready release with a catchy hook, safe redaction, useful examples, demo tasks, README copy, and launch messaging. Use when preparing a skill for GitHub, social sharing, marketplace submission, documentation, or community feedback.

日本語の概要は準備中です。原文の説明を表示しています。

Pre-share leak scanner for Claude Code skills (or any folder). Scans BEFORE you publish for secrets (API keys, tokens, private keys, .env values, high-entropy strings), PII (emails/phones), local machine paths (C:\Users\<name>, /home/<name>, /Users/<name>, UNC, internal hostnames), and client/proper-noun names from a LOCAL private dictionary; also flags service-specific code (jira/github/gitlab/slack/salesforce/notion/linear/ stripe/aws/google) that should be split into a dedicated service plugin. Use when the user says "sanitize this skill", "before sharing a skill", "check for leaks", "is this skill clean", "is this safe to commit/publish/ open-source", "scrub secrets", "redact before commit", or "pre-push leak check". Cross-platform, stdlib-only Python, fail-closed.

日本語の概要は準備中です。原文の説明を表示しています。

Install Codex skills into $CODEX_HOME/skills from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo (including private repos).

日本語の概要は準備中です。原文の説明を表示しています。

Teach software development through active project work while still producing a working result, maintaining bilingual English and Chinese project documentation, protecting private context, and publishing reviewed updates to GitHub only after confirmation. Use when Codex helps the user create, build, extend, debug, refactor, document, publish, or understand a software project and the user's goal includes learning, mentorship, guided implementation, pair programming, understanding the code, or becoming able to do similar work independently.

日本語の概要は準備中です。原文の説明を表示しています。

Review and resolve PR issues with Qodo - get AI-powered code review issues and fix them interactively (GitHub, GitLab, Bitbucket, Azure DevOps)

日本語の概要は準備中です。原文の説明を表示しています。

Review and resolve PR issues with Qodo - get AI-powered code review issues and fix them interactively (GitHub, GitLab, Bitbucket, Azure DevOps)

日本語の概要は準備中です。原文の説明を表示しています。

Find niches, topics, audiences, products, channels, and content angles via deep web search. Use whenever Ahmad says "find me a niche", "hunt niches in X", "what's an underserved audience for Y", "find similar sites/videos to <example>", "research the X market", "what are people building in Y space", "/niche-hunter X", or any phrasing that asks for niche / market / topic / audience / product / channel discovery across the open web. Trusts domain + keyword search; chains web_search → web_fetch / web_extract / web_crawl + reddit_search + search_youtube + github_repo_intel. NEVER uses awesome-list shortcuts. Output shape is FLEXIBLE — list, table, report, suggestions, or normal prose — picked from how Ahmad phrased the ask.

日本語の概要は準備中です。原文の説明を表示しています。

Scan open GitHub issues for dependencies, priority, parallel work, and staleness. Use to prioritize the backlog or pick what to do next. Don't use for one-issue analysis (/issue-analysis), resolving (/issue-resolver), or creating (/issue-creator).

日本語の概要は準備中です。原文の説明を表示しています。

Create structured GitHub issues from text, screenshots, or lists, with acceptance criteria and preserved reporter context. Use for filing bugs/features, batch creation, or template cleanup. Don't use for resolving, triaging, or deep issue analysis.

日本語の概要は準備中です。原文の説明を表示しています。

Create an atomic PR closing a GitHub issue end-to-end via a 6-step pipeline. Use to resolve, fix, or implement issue #N. Don't use for analysis without fixing (/issue-analysis), reviewing a PR (/issue-pr-review), or bulk backlog work (/auto-pilot).

日本語の概要は準備中です。原文の説明を表示しています。

Convert any phased plan file, or a conversation about what to build, into labelled GitHub issues under one tracking epic mapping each issue to its source task. No plan file required. Don't use for writing plans, resolving issues, or triage.

日本語の概要は準備中です。原文の説明を表示しています。

Analyze one GitHub issue for root cause, complexity, and risk into .idd/analysis-N.json. Use when you need to analyze or scope issue #N. Don't use for creating issues (/issue-creator), triaging (/issue-triage), or resolving (/issue-resolver).

日本語の概要は準備中です。原文の説明を表示しています。

Run an autonomous triage-resolve-review-merge loop to auto-pilot the GitHub issue backlog, resolving everything until done with zero prompts. Don't use for single-issue work (/issue-resolver), triage (/issue-triage), or PR review (/issue-pr-review).

日本語の概要は準備中です。原文の説明を表示しています。

Give a harness project its own GitHub-releases update checker: the Composer dependency, the name of the release archive, the per-project credential, the release workflow, and the five checks that catch an updater which is silently doing nothing. Use when a project should install its own releases, when a release is published and never offered, or when a hand-copied update checker should move to vendor/.

日本語の概要は準備中です。原文の説明を表示しています。

Orchestrate autonomous AI development pipelines through your Kanban board (Asana, GitHub Projects, Linear). Manages multi-worker Claude Code dispatch, deterministic quality gates, adversarial review, per-task cost tracking, and crash-proof pipeline execution.

日本語の概要は準備中です。原文の説明を表示しています。

Detect Git remote URL for GitHub integration

日本語の概要は準備中です。原文の説明を表示しています。

Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.

日本語の概要は準備中です。原文の説明を表示しています。

AI agent integration layer for the Pump SDK — agent instruction files, .well-known discovery, LLM context documents, 15+ skill files, MCP server prompts, and terminal management rules for GitHub Copilot and Gemini.

日本語の概要は準備中です。原文の説明を表示しています。

Fetch GitHub issues, spawn sub-agents to implement fixes and open PRs, then monitor and address PR review comments. Usage: /gh-issues [owner/repo] [--label bug] [--limit 5] [--milestone v1.0] [--assignee @me] [--fork user/repo] [--watch] [--interval 5] [--reviews-only] [--cron] [--dry-run] [--model glm-5] [--notify-channel -1002381931352]

日本語の概要は準備中です。原文の説明を表示しています。

Route Composio work between the hosted MCP-backed app and the local Composio CLI. Use when a user wants to read or act on external services such as email, calendars, GitHub, Slack, Notion, Linear, Jira, or CRMs; discover an integration or tool; recover a missing connection; combine multiple apps; or automate those actions with local files and scripts.

日本語の概要は準備中です。原文の説明を表示しています。

Prose final-pass editor for GitHub issue bodies, pull request bodies, release notes, README/docs changes, public comments, and user-facing explanations. Use when Codex drafts or revises substantial prose that will be published or committed, especially when the user asks to polish, de-slop, make it less AI-written, improve a PR/issue body, or prepare docs text; do not use for ordinary code implementation, debugging transcripts, logs, quoted text, command output, API names, or Chinese conversational replies unless explicitly requested.

日本語の概要は準備中です。原文の説明を表示しています。

Download and verify the seven platform FFmpeg archives produced for one rust-ffmpeg-splitter commit by GitHub Actions and CircleCI. Use when handing completed splitter CI binaries to rust-ffmpeg-sys without mixing commits or incomplete CI runs.

日本語の概要は準備中です。原文の説明を表示しています。

Hardcoded-secret detection — AWS keys, GitHub PATs, Slack tokens, Stripe keys, generic high-entropy strings. Pre-commit (`--staged-only`), explicit paths, or full repo. Use when guarding `git commit`, auditing a repo for leaked credentials, validating no secrets entered the diff before push, or producing a rotation list for an exposed-secret incident.

日本語の概要は準備中です。原文の説明を表示しています。