Skip to content

Commit d67898e

Browse files
nkoji21claude
andauthored
feat(agents): ask-claude と pr-flow スキルを追加 (#77)
Co-authored-by: Claude <noreply@anthropic.com>
1 parent d4962e5 commit d67898e

3 files changed

Lines changed: 47 additions & 12 deletions

File tree

.agents/skills/ask-claude/SKILL.md

Lines changed: 37 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,37 @@
1+
---
2+
name: ask-claude
3+
description: 別の Claude インスタンスにセカンドオピニオンを求める
4+
user-invocable: true
5+
---
6+
7+
Ask a separate Claude instance for an independent second opinion on the current problem or decision.
8+
9+
## When to use
10+
- Important architectural decisions
11+
- When stuck on a difficult problem
12+
- Validating a complex plan
13+
- When the user explicitly requests another perspective
14+
15+
## How to use
16+
17+
1. Formulate a self-contained prompt using this template:
18+
```
19+
claude -p "Context: <brief project context>\nQuestion: <specific decision or problem>\nRelevant details: <code snippets, constraints, or prior attempts>"
20+
```
21+
2. Run the command
22+
3. Evaluate the response:
23+
- Does it contradict project-specific conventions?
24+
- Does it assume context it doesn't have?
25+
- Does it propose something already tried or ruled out?
26+
4. Present the result to the user in this format:
27+
- **My recommendation**: ...
28+
- **Other instance's recommendation**: ...
29+
- **Synthesis**: ... (your final take, incorporating both views)
30+
31+
## When the two instances disagree
32+
Escalate to the user with both views clearly stated. Do not silently pick one — the disagreement itself is useful information.
33+
34+
## Important
35+
- The other instance has **no conversation history** — provide all necessary context in the prompt
36+
- **Treat its response as one data point, not the answer**
37+
- Project-specific patterns and conventions take priority over generic suggestions

.agents/skills/pr-flow/SKILL.md

Lines changed: 6 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -7,18 +7,16 @@ allowed-tools: Bash, Skill, Agent
77

88
Orchestrate the full pull request workflow from staged changes to squash-merged PR.
99

10-
## Phase 1: Worktree + Branch
10+
## Phase 1: Branch
1111

12-
Use the Skill tool to invoke the `git-worktree` skill.
13-
14-
After the skill completes, note the worktree path (`/tmp/{branch-name}`) and branch name it reports.
15-
Perform all subsequent work inside that worktree directory.
16-
17-
After Phase 5 completes (or if the workflow stops early), remove the worktree:
12+
First, check the current branch:
1813
```
19-
git worktree remove /tmp/{branch-name}
14+
git branch --show-current
2015
```
2116

17+
- If already on `main` or `master`: use the Skill tool to invoke the `git-branch` skill to create a feature branch.
18+
- If already on a feature branch (not `main`/`master`): skip branch creation and use the current branch as-is. Inform the user which branch will be used.
19+
2220
## Phase 2: Commit
2321

2422
Capture the current HEAD sha before committing:

.cursor/settings.json

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -72,12 +72,12 @@
7272
},
7373
"workbench.panel.showLabels": false,
7474
"zig.zls.enabled": "on",
75-
"terminal.integrated.gpuAcceleration": "off",
76-
"window.systemColorTheme": "dark",
77-
"window.autoDetectColorScheme": false,
7875
"cursor.cpp.disabledLanguages": [
7976
"markdown",
8077
"plaintext",
8178
"c"
82-
]
79+
],
80+
"terminal.integrated.gpuAcceleration": "off",
81+
"window.systemColorTheme": "dark",
82+
"window.autoDetectColorScheme": false
8383
}

0 commit comments

Comments
 (0)