القائمة
Expert-level decision policy for morph_fastapply, warpgrep_codebase_search, and warpgrep_github_search with strategic tool selection and execution patterns.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Quality gate and validation layer for Morph tool outputs, focusing on safety, correctness, and appropriate tool usage.
Autonomous multi-session browser testing engine with test synthesis, code-informed subflow planning, self-healing retry, run history persistence, viewport testing, and CI/CD integration. Uses `morph_browser_test_url` for browser automation.
Specialized skill for morph_preview_test_pr with PR-native browser verification, task formulation, and result interpretation guidance.
Automatic production site testing with code-aware analysis using warpgrep_codebase_search and morph_browser_test_url for comprehensive validation.
| name | morph-power-user |
| description | Expert-level decision policy for morph_fastapply, warpgrep_codebase_search, and warpgrep_github_search with strategic tool selection and execution patterns. |
Expert-level decision policy for morph_fastapply, warpgrep_codebase_search, warpgrep_github_search, morph_browser_test_url, and morph_preview_test_pr.
Guide strategic tool selection and execution patterns for Morph editing, search, and browser validation workflows. This skill focuses on what the plugin adds, when to use each Morph tool, when to fall back, and how to maximize success rate through proper preparation.
This plugin adds six practical Morph capabilities to Pi:
morph_fastapplywarpgrep_codebase_searchwarpgrep_github_searchmorph_browser_test_urlmorph_preview_test_prmorph_fastapplyeditwritewarpgrep_codebase_searchwarpgrep_github_searchmorph_browser_test_urlmorph_preview_test_predit and morph_fastapplyedit only for:
write for:
morph_fastapply by default for non-trivial existing-file edits:
Always use dry_run: true first when:
Skip dry run when:
Good anchors:
function calculateTotal(items) {
// ... existing code ...
}
Bad anchors:
// ... existing code ...
function calculateTotal(items) {
// ... existing code ...
}
Rules:
// ... existing code ... at the startAnchor Quality Metrics:
| Metric | Good | Fair | Poor |
|---|---|---|---|
| Uniqueness | 1 match | 2-3 matches | 4+ matches |
| Context lines | 3+ distinctive | 2 distinctive | 1 or generic |
| Specificity | Function signature | Variable name | Generic comment |
Use warpgrep_codebase_search when:
Use warpgrep_github_search when:
Fall back to native tools when:
Use morph_browser_test_url when:
Use morph_preview_test_pr when:
Fall back to manual browser tools when:
1. warpgrep_codebase_search "find all usages of oldFunction"
2. Read each file identified
3. morph_fastapply with dry_run: true for each file
4. Review diffs
5. morph_fastapply with dry_run: false to apply
6. Run tests
1. warpgrep_codebase_search "how is authentication handled"
2. Read relevant files
3. Identify edit targets
4. morph_fastapply with dry_run: true
5. Validate approach with user if significant
6. Apply changes
1. warpgrep_github_search "owner/repo implementation of feature X"
2. Analyze results
3. Adapt pattern to local codebase
4. Use morph_fastapply unless the change is a tiny exact one-block replacement
1. warpgrep_codebase_search "find all files importing module X"
2. Create change plan (list files and changes)
3. For each file:
a. Read file
b. morph_fastapply with dry_run: true
c. Review diff
4. If all diffs look good:
a. Apply all changes
b. Run tests
5. If any diff is wrong:
a. Adjust anchors for that file
b. Retry from step 3
Scenario: Rename getUserData to fetchUserProfile across 5 files
Good approach:
// Step 1: Find all usages
warpgrep_codebase_search "getUserData function call import"
// Step 2: For each file, use FastApply with good anchors
// File: src/api/users.ts
export async function getUserData(userId: string) {
// ... existing code ...
}
// File: src/components/Profile.tsx
import { getUserData } from '../api/users';
// ... existing code ...
const data = await getUserData(user.id);
Bad approach:
// Using generic anchors
// ... existing code ...
getUserData
// ... existing code ...
Scenario: Add email validation to 3 form components
Good approach:
// Step 1: Find all form components
warpgrep_codebase_search "form onSubmit email input"
// Step 2: Read each component to understand structure
// Step 3: Use FastApply with component-specific anchors
// ContactForm.tsx
const handleSubmit = (e: FormEvent) => {
e.preventDefault();
// ... existing code ...
};
// SignupForm.tsx
function SignupForm() {
// ... existing code ...
const onSubmit = async (data: FormData) => {
// ... existing code ...
};
}
Scenario: Change API base URL from /api/v1 to /api/v2
Good approach:
// Step 1: Find all API calls
warpgrep_codebase_search "fetch axios /api/v1"
// Step 2: Group by file and review
// Step 3: Use FastApply with endpoint-specific anchors
// api/client.ts
const BASE_URL = '/api/v1';
// ... existing code ...
// services/users.ts
fetch('/api/v1/users')
// ... existing code ...
Symptoms:
Diagnosis:
// Check anchor uniqueness
warpgrep_codebase_search "[your-anchor-pattern] [filename]"
// If multiple results, anchor is ambiguous
Solution:
Symptoms:
Diagnosis:
Solution:
Symptoms:
Diagnosis:
Solution:
Symptoms:
Diagnosis:
Solution:
rg with regexSymptoms:
Diagnosis:
Solution:
When to use:
Process:
For each file:
1. Read file
2. FastApply with dry_run
3. Review diff
4. Apply if good
5. Test
6. Move to next file
When to use:
Process:
1. Read all files
2. FastApply dry_run for all
3. Review all diffs together
4. If all good, apply all
5. Run comprehensive tests
6. If any fail, rollback and use Sequential
When to use:
Process:
1. Identify dependency order
2. Start with lowest dependency (API, types)
3. Apply and test
4. Move up dependency chain
5. Apply and test each level
6. Final integration test
Before applying FastApply, validate anchors:
// Count occurrences
warpgrep_codebase_search "[anchor-pattern] [filename]"
// Expected: 1 result
// If 0: anchor doesn't exist, adjust
// If 2+: anchor is ambiguous, add more context
For complex edits:
1. Start with broad WarpGrep search
2. Narrow down to relevant files
3. Read files to understand structure
4. Create detailed change plan
5. Apply changes incrementally
6. Test after each increment
When Morph tools fail:
1. Try morph_fastapply
↓ (if fails)
2. Adjust anchors and retry
↓ (if still fails)
3. Fall back to native edit only for tiny exact one-block replacements
↓ (if fails)
4. Read file again and reassess
↓ (if still fails)
5. Ask user for guidance
morph_fastapply without reading the file firstmorph_fastapply for brand new filesWhen morph_fastapply fails:
edit only if the change is a tiny exact one-block replacementWhen warpgrep_codebase_search fails:
bash with rg for pattern matchingread to inspect matching filesWhen warpgrep_github_search fails:
github_search_code for exact symbol searchgithub_get_file_contents if you know the pathThis skill assumes:
routing.editMode: "force" or "strong" for FastApply preferencerouting.codebaseSearchMode: "force" or "strong" for local WarpGreprouting.githubSearchMode: "force" or "strong" for GitHub WarpGreprouting.fallbackToNativeTools: true for automatic fallbackAdjust behavior if user has different routing modes configured.