adapting-claude-pipeline

Name: adapting-claude-pipeline
Author: aaddrick

120stars16forks

How to install adapting-claude-pipeline?

aaddrick/claude-pipeline/adapting-claude-pipeline

$npx -y skills add aaddrick/claude-pipeline --skill adapting-claude-pipeline

Installs into the current project.

Summary

Use when adapting the generic .claude pipeline folder to a specific codebase - adjusting skills, agents, hooks, scripts, prompts, and settings for the target project's tech stack and workflows

Files · 1

View on GitHub

SKILL.md

1	# Adapting Claude Pipeline to a Codebase
2
3	## Overview
4
5	Adapt the generic `.claude/` pipeline folder to a specific project's tech stack, domain, and workflows. This means modifying, replacing, or removing every skill, agent, hook, script, prompt, and setting so they serve the target codebase — not the original Laravel/web template.
6
7	Core principle: Every file in `.claude/` must earn its place. If it doesn't serve the target project, delete it. If it needs modification, modify it. If new capabilities are needed, create them.
8
9	## When to Use
10
11	- Cloning the claude-pipeline repo into a new project
12	- Onboarding an existing codebase with the generic `.claude/` folder
13	- Switching tech stacks (e.g., Laravel to Python, web to CLI, monolith to microservices)
14
15	## The Process
16
17	```dot
18	digraph adaptation {
19	rankdir=TB;
20
21	"1. Brainstorm with user" [shape=box style=filled fillcolor=lightyellow];
22	"2. Research domain patterns" [shape=box];
23	"3. Audit existing .claude/ inventory" [shape=box];
24	"4. Write adaptation plan" [shape=box];
25	"5. Execute plan with subagents" [shape=box style=filled fillcolor=lightblue];
26	"6. Verify adapted pipeline" [shape=box style=filled fillcolor=lightgreen];
27
28	"1. Brainstorm with user" -> "2. Research domain patterns";
29	"2. Research domain patterns" -> "3. Audit existing .claude/ inventory";
30	"3. Audit existing .claude/ inventory" -> "4. Write adaptation plan";
31	"4. Write adaptation plan" -> "5. Execute plan with subagents";
32	"5. Execute plan with subagents" -> "6. Verify adapted pipeline";
33	}
34	```
35
36	---
37
38	### Phase 1: Brainstorm
39
40	REQUIRED: Use the `brainstorming` skill to explore the target project.
41
42	Focus questions on:
43	- Tech stack: Language, framework, database, infrastructure
44	- Project type: Web app, CLI tool, library, API, microservice, data pipeline, etc.
45	- Team workflows: CI/CD, code review, deployment, testing patterns
46	- Pain points: What does the team struggle with that agents could help?
47	- Existing tooling: Linters, formatters, test runners, build systems
48	- Scope: Full adaptation or partial (e.g., keep orchestration, replace agents)?
49
50	Key decisions to reach:
51	1. Which existing skills/agents/hooks are relevant (keep/modify)?
52	2. Which are irrelevant (delete)?
53	3. What new capabilities does the project need?
54	4. What domain-specific best practices should agents follow?
55
56	### Phase 2: Research Domain Patterns
57
58	Use WebSearch to investigate the target project's domain. This feeds directly into agent definitions and skill content.
59
60	Search for:
61	```
62	"[language/framework] best practices [current year]"
63	"[language/framework] anti-patterns"
64	"[language/framework] code review checklist"
65	"[language/framework] common mistakes"
66	"[language/framework] testing best practices"
67	"[language/framework] security considerations"
68	"[language/framework] project structure conventions"
69	"[tool/framework] CI/CD pipeline best practices"
70	```
71
72	Capture findings as notes — they will be incorporated into:
73	- Agent anti-patterns sections
74	- Skill content (technique skills)
75	- Hook logic (formatting, linting)
76	- Orchestration script stages
77
78	### Phase 3: Audit Existing Inventory
79
80	Categorize every `.claude/` file into one of four buckets:
81
82	\| Bucket \| Action \| Example \|
83	\|--------\|--------\|---------\|
84	\| Keep as-is \| Universal process skills \| brainstorming, writing-plans, TDD, systematic-debugging \|
85	\| Modify \| Adapt to new tech stack \| implement-issue (change test commands), agents (change domain) \|
86	\| Replace \| Same purpose, different implementation \| laravel-backend-developer → python-backend-developer \|
87	\| Delete \| Irrelevant to target project \| bulletproof-frontend (for a CLI tool), write-docblocks (non-PHP) \|
88
89	#### Inventory Checklist
90
91	Skills (19 in template):
92
93	\| Skill \| Category \| Typical Decision \|
94	\|-------\|----------\|-----------------\|
95	\| brainstorming \| Process \| Keep as-is \|
96	\| bulletproof-frontend \| Domain (web/CSS) \| Delete if not web \|
97	\| dispatching-parallel-agents \| Process \| Keep as-is \|
98	\| executing-plans \| Process \| Keep as-is \|
99	\| handle-issues \| Workflow (GitHub) \| Keep if using GitHub Issues \|
100	\| implement-issue \| Workflow (GitHub) \| Keep if using GitHub Issues \|
101	\| investigating-codebase-for-user-stories \| Process \| Keep as-is \|
102	\| process-pr \| Workflow (GitHub) \| Keep if using GitHub PRs \|
103	\| review-ui \| Domain (web/CSS) \| Delete if not web \|
104	\| subagent-driven-development \| Process \| Keep as-is \|
105	\| systematic-debugging \| Process \| Keep as-is \|
106	\| test-driven-development \| Process \| Keep as-is \|
107	\| ui-design-fundamentals \| Domain (web/CSS) \| Delete if not web \|
108	\| using-git-worktrees \| Process \| Keep as-is \|
109	\| using-skills \| Meta \| Keep as-is \|
110	\| write-docblocks \| Domain (PHP) \| Replace wit

People who liked this also viewed

6 picks

Type

adapting-claude-pipeline

120stars16forks

View on GitHub

How to install adapting-claude-pipeline?

aaddrick/claude-pipeline/adapting-claude-pipeline

$npx -y skills add aaddrick/claude-pipeline --skill adapting-claude-pipeline

Installs into the current project.

Summary

Use when adapting the generic .claude pipeline folder to a specific codebase - adjusting skills, agents, hooks, scripts, prompts, and settings for the target project's tech stack and workflows

Files · 1

View on GitHub

SKILL.md

1	# Adapting Claude Pipeline to a Codebase
2
3	## Overview
4
5	Adapt the generic `.claude/` pipeline folder to a specific project's tech stack, domain, and workflows. This means modifying, replacing, or removing every skill, agent, hook, script, prompt, and setting so they serve the target codebase — not the original Laravel/web template.
6
7	Core principle: Every file in `.claude/` must earn its place. If it doesn't serve the target project, delete it. If it needs modification, modify it. If new capabilities are needed, create them.
8
9	## When to Use
10
11	- Cloning the claude-pipeline repo into a new project
12	- Onboarding an existing codebase with the generic `.claude/` folder
13	- Switching tech stacks (e.g., Laravel to Python, web to CLI, monolith to microservices)
14
15	## The Process
16
17	```dot
18	digraph adaptation {
19	rankdir=TB;
20
21	"1. Brainstorm with user" [shape=box style=filled fillcolor=lightyellow];
22	"2. Research domain patterns" [shape=box];
23	"3. Audit existing .claude/ inventory" [shape=box];
24	"4. Write adaptation plan" [shape=box];
25	"5. Execute plan with subagents" [shape=box style=filled fillcolor=lightblue];
26	"6. Verify adapted pipeline" [shape=box style=filled fillcolor=lightgreen];
27
28	"1. Brainstorm with user" -> "2. Research domain patterns";
29	"2. Research domain patterns" -> "3. Audit existing .claude/ inventory";
30	"3. Audit existing .claude/ inventory" -> "4. Write adaptation plan";
31	"4. Write adaptation plan" -> "5. Execute plan with subagents";
32	"5. Execute plan with subagents" -> "6. Verify adapted pipeline";
33	}
34	```
35
36	---
37
38	### Phase 1: Brainstorm
39
40	REQUIRED: Use the `brainstorming` skill to explore the target project.
41
42	Focus questions on:
43	- Tech stack: Language, framework, database, infrastructure
44	- Project type: Web app, CLI tool, library, API, microservice, data pipeline, etc.
45	- Team workflows: CI/CD, code review, deployment, testing patterns
46	- Pain points: What does the team struggle with that agents could help?
47	- Existing tooling: Linters, formatters, test runners, build systems
48	- Scope: Full adaptation or partial (e.g., keep orchestration, replace agents)?
49
50	Key decisions to reach:
51	1. Which existing skills/agents/hooks are relevant (keep/modify)?
52	2. Which are irrelevant (delete)?
53	3. What new capabilities does the project need?
54	4. What domain-specific best practices should agents follow?
55
56	### Phase 2: Research Domain Patterns
57
58	Use WebSearch to investigate the target project's domain. This feeds directly into agent definitions and skill content.
59
60	Search for:
61	```
62	"[language/framework] best practices [current year]"
63	"[language/framework] anti-patterns"
64	"[language/framework] code review checklist"
65	"[language/framework] common mistakes"
66	"[language/framework] testing best practices"
67	"[language/framework] security considerations"
68	"[language/framework] project structure conventions"
69	"[tool/framework] CI/CD pipeline best practices"
70	```
71
72	Capture findings as notes — they will be incorporated into:
73	- Agent anti-patterns sections
74	- Skill content (technique skills)
75	- Hook logic (formatting, linting)
76	- Orchestration script stages
77
78	### Phase 3: Audit Existing Inventory
79
80	Categorize every `.claude/` file into one of four buckets:
81
82	\| Bucket \| Action \| Example \|
83	\|--------\|--------\|---------\|
84	\| Keep as-is \| Universal process skills \| brainstorming, writing-plans, TDD, systematic-debugging \|
85	\| Modify \| Adapt to new tech stack \| implement-issue (change test commands), agents (change domain) \|
86	\| Replace \| Same purpose, different implementation \| laravel-backend-developer → python-backend-developer \|
87	\| Delete \| Irrelevant to target project \| bulletproof-frontend (for a CLI tool), write-docblocks (non-PHP) \|
88
89	#### Inventory Checklist
90
91	Skills (19 in template):
92
93	\| Skill \| Category \| Typical Decision \|
94	\|-------\|----------\|-----------------\|
95	\| brainstorming \| Process \| Keep as-is \|
96	\| bulletproof-frontend \| Domain (web/CSS) \| Delete if not web \|
97	\| dispatching-parallel-agents \| Process \| Keep as-is \|
98	\| executing-plans \| Process \| Keep as-is \|
99	\| handle-issues \| Workflow (GitHub) \| Keep if using GitHub Issues \|
100	\| implement-issue \| Workflow (GitHub) \| Keep if using GitHub Issues \|
101	\| investigating-codebase-for-user-stories \| Process \| Keep as-is \|
102	\| process-pr \| Workflow (GitHub) \| Keep if using GitHub PRs \|
103	\| review-ui \| Domain (web/CSS) \| Delete if not web \|
104	\| subagent-driven-development \| Process \| Keep as-is \|
105	\| systematic-debugging \| Process \| Keep as-is \|
106	\| test-driven-development \| Process \| Keep as-is \|
107	\| ui-design-fundamentals \| Domain (web/CSS) \| Delete if not web \|
108	\| using-git-worktrees \| Process \| Keep as-is \|
109	\| using-skills \| Meta \| Keep as-is \|
110	\| write-docblocks \| Domain (PHP) \| Replace wit

People who liked this also viewed

6 picks

Type