Wednesday Git
wednesday-solutions/ai-agent-skills
Unified Git workflow. An agent skill from wednesday-solutions/ai-agent-skills.
Context-aware Q&A with auto context gathering. An agent skill from sd0xdev/sd0x-harness.
$ npx skills add sd0xdev/sd0x-harness --skill ask -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install sd0xdev/sd0x-harness ask --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/sd0xdev/sd0x-harness.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/ask .claude/skills/ask && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "ask" agent skill from https://github.com/sd0xdev/sd0x-harness/tree/main/skills/ask into .claude/skills/ask/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ask", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/sd0xdev/sd0x-harness/tree/main/skills/askType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add sd0xdev/sd0x-harness --skill ask -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install sd0xdev/sd0x-harness ask --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sd0xdev/sd0x-harness.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/ask .agents/skills/ask && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "ask" agent skill from https://github.com/sd0xdev/sd0x-harness/tree/main/skills/ask into .agents/skills/ask/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ask", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add sd0xdev/sd0x-harness --skill ask -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install sd0xdev/sd0x-harness ask --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sd0xdev/sd0x-harness.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/ask .cursor/skills/ask && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "ask" agent skill from https://github.com/sd0xdev/sd0x-harness/tree/main/skills/ask into .cursor/skills/ask/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ask", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/sd0xdev/sd0x-harness.git --path skills/ask--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add sd0xdev/sd0x-harness --skill ask -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install sd0xdev/sd0x-harness ask --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sd0xdev/sd0x-harness.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/ask .gemini/skills/ask && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "ask" agent skill from https://github.com/sd0xdev/sd0x-harness/tree/main/skills/ask into .gemini/skills/ask/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ask", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install sd0xdev/sd0x-harness askInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add sd0xdev/sd0x-harness --skill ask -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/sd0xdev/sd0x-harness.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/ask .github/skills/ask && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "ask" agent skill from https://github.com/sd0xdev/sd0x-harness/tree/main/skills/ask into .github/skills/ask/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ask", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add sd0xdev/sd0x-harness --skill ask -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install sd0xdev/sd0x-harness ask --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sd0xdev/sd0x-harness.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/ask .opencode/skills/ask && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "ask" agent skill from https://github.com/sd0xdev/sd0x-harness/tree/main/skills/ask into .opencode/skills/ask/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ask", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
askContext-aware Q&A with auto context gathering. An agent skill from sd0xdev/sd0x-harness.
Ask is an agent skill from sd0xdev/sd0x-harness. Context-aware Q&A with auto context gathering. Use when: user has a quick question about codebase, git history, rules, docs, or skills during development. Not for: code changes (use feature-dev), code review (use codex-review-fast), deep research (use deep-research), full code trace (use code-explore). Output: structured answer with source attribution.
Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/intent-patterns.md` and `references/routing-table.md`).
It sits in Development, covering Deep research and Git workflow. It works with Git and Bash. The repository describes itself as: The harness layer for Claude Code — a reference implementation of harness engineering with hook-enforced dual review, state-machine gates that survive context compaction, and… The licence is MIT.
5 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit c9a2036. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
ReadGrepGlobBash(git:*)Bash(node:*)AgentFrom allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
gitFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Ask loads about 2.1k tokens when it runs, and up to ~3.2k if it reads all its reference files. Until then it costs about 90 tokens; SKILL.md has 830 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check noted patterns worth knowing about, such as sudo or a known installer.
| Secret skip | Do not read `.env`, `credentials.*`, `*secret*` files |Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from sd0xdev/sd0x-harness at commit c9a2036, republished under its MIT licence (© sd0xdev). 830 words, ~2,093 tokens.
.claude/skills/ask/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.| Scenario | Alternative |
|---|---|
| Code modification or implementation | /feature-dev |
| Code review or PR review | /codex-review-fast |
| Tech spec review | /review-spec |
| Document review | /codex-review-doc |
| Bug fixing | /bug-fix |
| Next step decision | /next-step |
| Deep multi-source research | /deep-research |
| Systematic code tracing | /code-explore |
Run these 4 commands in parallel to build session context:
| # | Action | Tool |
|---|---|---|
| 1 | Current branch | Bash("git branch --show-current") |
| 2 | Feature detection | Bash("node scripts/resolve-feature.js") — the wrapper, not the CLI: it owns the failure payload, so a resolver that runs and fails — nonzero exit, signal, truncated write, off-contract payload — still yields the full shape with scan_error: true rather than {} or a truncated document. A missing node yields no JSON at all; treat that like any other unusable payload |
| 2b | scan_error gate | scan_error !== false ⇒ the source sets are unknown, not empty — report and take the ⚠️ Need Human exit rather than answering from an empty set. Gate on !== false, not === true: a {} payload from a shell fallback has no such field, so a non-null key is not evidence the sets are complete |
| 3 | Changed files | Bash("git status --porcelain") |
| 4 | Recent commits | Bash("git log --oneline -5") |
Untracked file fallback: If feature resolver returns key: null, derive feature from changed/untracked paths:
git status --porcelain output for docs/features/<key>/ or skills/<key>/ patterns<key> as candidate featuredocs intent feature-first lookup when resolver failsBefore classifying intent, review prior conversation turns for:
Use this context to disambiguate the question and select the right intent. See references/intent-patterns.md for edge cases.
Classify the question (LLM-inferred) into one or more intents:
| Intent | Signal Examples | Context Actions |
|---|---|---|
code | "function X 做什麼", file paths, module names | Grep → Read → trace 1 level |
git | "最近改了什麼", "誰改的", "when" | git log / diff / blame |
docs | "需求是什麼", "spec 寫了什麼" | Feature resolve → source set by question kind → fallback Glob |
rules | "規則是什麼", "convention", "allowed" | Read rules/ files |
skill | "有沒有 skill", "怎麼用 /X" | Glob skills/ → Read SKILL.md |
arch | "系統架構", "整體設計" | CLAUDE.md + Explore agent |
multi | Multiple intents mixed | Combine actions from each intent |
Before gathering context, check if the question is action-oriented. See references/routing-table.md.
If a better skill is identified, suggest it: "這個問題更適合 /X,要改用嗎?" — do not auto-redirect.
Execute per-intent tool call sequences. Hard limits apply.
code: Grep keywords (top 10 files) → Read most relevant (max 5) → trace imports (1 level)
git: git log --oneline -20 → git diff (if recent changes) → git blame (if specific lines)
docs: Resolve feature → pick the source set the question actually asks for → fallback Glob "docs/**/*.md" (top 5) → Read (max 3)
| The question is… | Read | Not |
|---|---|---|
| "現在的行為是什麼" | code, rules/, current_authority | A tech spec — it records the design, not what shipped |
| "當初為什麼這樣設計" | design_records | — |
| "當初要求什麼 / 這張單結了嗎" | work_records | — |
| "這個決定是什麼時候做的" | history_records | — |
Answering a current-behaviour question from a design record is the specific failure this split exists to prevent: the spec is the older artifact, so it reads as authoritative and is wrong. When a design record is the only source available, say which document the answer came from and that it may predate the code.
rules: Glob rules/*.md + .claude/rules/*.md → Grep keywords → Read + quote (max 3)
skill: Glob skills/*/SKILL.md → Grep keywords (top 5) → Read (max 3)
arch: Read CLAUDE.md + key entrypoints → dispatch Explore agent
multi: Combine steps from each intent. Parallel execution. Hard limit: max 8 file reads total.
| Complexity | Criteria | Strategy |
|---|---|---|
| Simple | Single intent, clear target, < 5 files | Direct tools only (0 agents) |
| Medium | Multi-file, cross-module | 1 Explore agent |
| Complex | Multi-intent, cross-cutting | 2 agents parallel (hard max) |
Dispatch when: Grep returns > 10 files across modules, or question involves architecture / cross-cutting concerns. Default: direct tool calls.
Combine all gathered context into a structured answer. Follow the output format below.
This skill is strictly read-only. The following git commands are prohibited:
git add | git commit | git push | git pull | git reset | git stash
git rebase | git merge | git checkout -- | git restore | git cleanallowed-tools does not include Edit, Write, or NotebookEdit.
| Control | Rule |
|---|---|
| Repo boundary | All Read/Glob within repo root (git rev-parse --show-toplevel) |
| Traversal rejection | Reject .. path segments, absolute paths outside repo, symlinks out of repo |
| Secret skip | Do not read .env, credentials.*, *secret* files |
| Output redaction | High-confidence secret patterns → [REDACTED]; medium-confidence → mask with 4 chars visible |
## Answer
{Direct, concise answer}
### Sources
| Type | Reference | Relevance |
|------|-----------|-----------|
| file | `path/file.js:42` | {why relevant} |
| commit | `abc1234 — message` | {why relevant} |
| command | `git log --oneline -5` | {result summary} |
### See Also
- `/code-explore` — for full trace
- {other relevant skill or doc}Every claim must have at least one source evidence. Answer < 500 words unless user requests detail.
references/intent-patterns.md — Detailed intent examples and edge cases (read when classifying ambiguous questions)references/routing-table.md — Full skill routing decision table (read when checking if another skill is better)Input: /ask resolve-feature-cli.js 怎麼偵測 feature?
Phase 0: branch=feat/ask, feature=ask
Phase 1: Intent=code (file path mentioned)
Phase 2: Grep "resolve-feature" → Read scripts/lib/feature-resolver.js → trace exports
Phase 4: Answer with Sources (file evidence)Input: /ask 最近有什麼 commit?
Phase 0: branch=feat/ask
Phase 1: Intent=git ("最近", "commit")
Phase 2: git log --oneline -20
Phase 4: Answer with Sources (commit + command evidence)Input: /ask auto-loop 的規則是什麼?有哪些 skill 會用到?
Phase 0: branch=feat/ask
Phase 1: Intent=multi (rules + skill)
Phase 2: Read rules/auto-loop.md + Grep "auto-loop" in skills/*/SKILL.md
Phase 4: Answer with Sources (file evidence from both rules and skills)© sd0xdev, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 2 other files (references) in skills/ask of sd0xdev/sd0x-harness.
Open the folder on GitHubat commit c9a2036
Ask next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Ask this skillsd0xdev/sd0x-harness | 192 | — | ~2.1k | Automated safety check: Notes | MIT | |
| Wednesday Gitwednesday-solutions/ai-agent-skills | 170 | — | ~702 | Automated safety check: Pass | MIT | |
| Speckit Git Featurekunstmusik/blue | 154 | 4 repos | ~861 | Automated safety check: Pass | GPL-3.0 | |
| Trace And Isolaterohitg00/skillkit | 1.5k | — | ~1.8k | Automated safety check: Pass | Apache-2.0 | |
| Speckit Git Initializekunstmusik/blue | 154 | 5 repos | ~438 | Automated safety check: Pass | GPL-3.0 | |
| Tapd Iteration InitTencentBlueKing/bk-bcs | 840 | — | ~1.3k | Automated safety check: Pass | Custom licence |
wednesday-solutions/ai-agent-skills
Unified Git workflow. An agent skill from wednesday-solutions/ai-agent-skills.
kunstmusik/blue
Create a feature branch with sequential or timestamp numbering
rohitg00/skillkit
Applies systematic tracing and isolation techniques to pinpoint exactly where a bug originates in code.
kunstmusik/blue
Initialize a Git repository with an initial commit. An agent skill from kunstmusik/blue.
TencentBlueKing/bk-bcs
迭代执行流水线启动器。分三个阶段执行:信息检查(验证 git 环境、获取迭代信息、 解析迭代分支)→ 恢复检测(已有状态文件时判定恢复策略)→ 新流程初始化(创建分支、 迭代目录和 iteration-state.json)。
NVIDIA/skills
Autonomous NeMo-RL research agent workflow for directed hypothesis testing and open-ended discovery.
sd0xdev/sd0x-harness
Write an Architecture Decision Record (ADR) for a feature — Context / Decision / Status / Consequences / Alternatives, filed as docs/features/<feature/adr-<NNN-<title.md with a 3-digit zero-padded…
sd0xdev/sd0x-harness
Load GitHub PR review comments into AI session — analyze, triage, plan.
sd0xdev/sd0x-harness
Change-aware next step advisor. An agent skill from sd0xdev/sd0x-harness.
sd0xdev/sd0x-harness
Obsidian vault integration via official CLI. An agent skill from sd0xdev/sd0x-harness.
sd0xdev/sd0x-harness
Agent-driven workflow orchestration (v1 report-only). An agent skill from sd0xdev/sd0x-harness.
sd0xdev/sd0x-harness
Post friendly review comments to a GitHub PR — prepare locally, preview, then submit as atomic review.
Categories
Context-aware Q&A with auto context gathering. An agent skill from sd0xdev/sd0x-harness. Ask is an agent skill from sd0xdev/sd0x-harness. Context-aware Q&A with auto context gathering.
Ask fits situations like: : user has a quick question about codebase; skills during development.
Run `npx skills add sd0xdev/sd0x-harness --skill ask -a claude-code`. Or copy the skill folder (skills/ask in sd0xdev/sd0x-harness) into .claude/skills/ask in your project. Claude Code loads it when a task matches its description.
Run `npx skills add sd0xdev/sd0x-harness --skill ask -a codex`. Or copy the skill folder (skills/ask in sd0xdev/sd0x-harness) into .agents/skills/ask in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sd0xdev/sd0x-harness --skill ask -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ask, .gemini/skills/ask, .github/skills/ask and .opencode/skills/ask in your project.
Going by SKILL.md and its folder, Ask needs the command-line tools its instructions call (git). Its frontmatter pre-approves these tools: Read, Grep, Glob, Bash(git:*), Bash(node:*), Agent.
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
Ask is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.1k tokens (SKILL.md is roughly 8.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.1k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Ask: Wednesday Git (wednesday-solutions/ai-agent-skills, 170 stars), Speckit Git Feature (kunstmusik/blue, 154 stars), Trace And Isolate (rohitg00/skillkit, 1.5k stars) and Speckit Git Initialize (kunstmusik/blue, 154 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
sd0xdev (a GitHub user) maintains it in sd0xdev/sd0x-harness, which has 192 GitHub stars. The repository holds 91 skills in this directory. The repository was last updated on October 6, 2026.
Source: sd0xdev/sd0x-harness on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.