Agent skill · Frontend

re-architecture

Pipeline Component Analysis & Feedback Tool. Decomposes pipelines into components with traceability feedback. Records all interactions in Machine-Readable YAML format. Integrates with /research skill for skill-driven pipeline support.

majiayu000github.com/majiayu000GitHub ↗
claude-codecan modify filesMIT
Install
npx skills add majiayu000/claude-skill-registry --skill re-architecture --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 7 KB
Bundled scripts: none
Version: 1.0.0
Allowed tools: -Read-Grep-Glob-Task-Write-Edit
Path: skills/analysis/re-architecture/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# /re-architecture - Pipeline Component Analysis & Feedback > **Version:** 1.0.0 | **Model:** opus --- ## Overview | Aspect | Description | |--------|-------------| | **Purpose** | Decompose pipelines into components with traceability feedback | | **Output** | L1: Summary / L2: Per-component analysis / L3: YAML log with full traceability | | **Language** | All output in Korean | --- ## Cross-Skill Integration | Skill | Relationship | |-------|--------------| | `/research` | Handoff for deep research after analysis | | `/planning` | Implementation planning after research | --- ## Commands | Command | Description | |---------|-------------| | `<target-path>` | Analyze pipeline at specified path | | `--resume <slug>` | Resume previous analysis session | --- ## Execution Flow ### Phase 1: Decomposition 1. Parse target path from arguments 2. Analyze pipeline structure with Sequential Thinking 3. Extract components, stages, and dependencies 4. Update YAML log with decomposition results 5. Present results to user ### Phase 2: Iterative Component Analysis For each component: 1. Deep analysis of component structure 2. Record analysis in YAML log (before) 3. Generate feedback (findings, reco

What's inside
Steps it walks through
  1. Overview
  2. Cross-Skill Integration
  3. Commands
  4. Execution Flow
  5. Phase 1: Decomposition
  6. Phase 2: Iterative Component Analysis
  7. Phase 3: Handoff Preparation
  8. YAML Log Schema
  9. Output Format
  10. Round Presentation
  11. L1 Return Summary
  12. User Interaction Options
  13. Component Analysis Options
  14. Handoff Options
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
descriptive-statisticsSummarizing and visualizing data through measures of center, spread, shape, and position. Covers…Data & Analyticsperplexity-researcher-reasoning-proHighest level of research and reasoning capabilities for complex decision-making with significant…OtherretroBrutally honest engineering retrospective. Analyzes git history for what actually happened — not…Data & AnalyticsanalyzeUniversal multi-perspective analyzer for any topic, file, idea, or decision. Extract key points…Otherarize-prompt-optimizationINVOKE THIS SKILL when optimizing, improving, or debugging LLM prompts using production trace data…Data & Analyticscellxgene-contextGuide for integrating CellxGene Census single-cell data with ENCODE bulk experiments. Use when…Data & Analytics
About this skill
What does the re-architecture skill do?

Pipeline Component Analysis & Feedback Tool. Decomposes pipelines into components with traceability feedback. Records all interactions in Machine-Readable YAML format. Integrates with /research skill for skill-driven pipeline support.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill re-architecture --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going
All skills →
The full catalog, by category and by tool.
Open Source Radar →
The repositories these skills come from, watched daily.
The people behind them →
Makers and builders across the ecosystem.