Agent skill

architectural-decisions

Use when encountering questions about WHY code is built a certain way, when about to make architectural changes (new patterns, restructuring, choosing between approaches), or when the user asks about design rationale in a Repowise-indexed codebase (.repowise/ directory exists). Also activates when commit messages or code comments contain decision signals like "WHY:", "DECISION:", "TRADEOFF:", "ADR:".

Stars 1,072
Forks 161

Install this agent skill to your Project

npx add-skill https://github.com/repowise-dev/repowise/tree/main/plugins/claude-code/skills/architectural-decisions

SKILL.md

Architectural Decisions with Repowise

Repowise captures architectural decisions — the why behind how code is built.

When the user asks "why is X built this way?"

Call get_why(query="X") to search across all captured decisions. This searches:

  • Inline decision markers in code (# WHY:, # DECISION:, # TRADEOFF:)
  • Decisions extracted from git history (migrations, refactors)
  • Decisions mined from documentation

When about to make an architectural change

  1. Call get_why(query="the specific area you're changing") to find existing decisions that govern that area.
  2. If decisions are found, present them to the user before proceeding — they may not want to contradict an existing architectural choice.
  3. If no decisions are found, proceed but note that no recorded decision governs this area.

When called with no specific query

Call get_why() with no arguments to get the decision health dashboard:

  • Stale decisions that may no longer apply
  • Ungoverned hotspots (high-churn files with no recorded decisions)

When a file has decision markers

If you see # WHY:, # DECISION:, # TRADEOFF:, or # ADR: comments in code, call get_context(targets=["that_file.py"]) to see the full decision record with context and affected modules.

Recording new decisions

If the user makes an architectural decision during the conversation, suggest: "Want to record this decision? Add a # DECISION: comment in the relevant code, or run repowise decision add to capture it formally."

Expand your agent's capabilities with these related and highly-rated skills.

repowise-dev/repowise

codebase-exploration

Use when exploring, understanding, or answering questions about a codebase that has Repowise indexed (indicated by a .repowise/ directory in the project root). Activates for questions like "how does X work", "explain the architecture", "where is Y implemented", "what does this module do", or any task requiring understanding of codebase structure before diving into source files.

1,072 161
Explore
repowise-dev/repowise

dead-code-cleanup

Use when the user asks about cleanup, removing unused code, refactoring, reducing bundle size, or identifying dead code in a Repowise-indexed codebase (.repowise/ directory exists). Also activates when discussing technical debt, code hygiene, or repository maintenance.

1,072 161
Explore
repowise-dev/repowise

pre-modification-check

Use before modifying, refactoring, or deleting files in a codebase that has Repowise indexed (indicated by a .repowise/ directory). Activates when Claude is about to edit code, especially shared utilities, core modules, or files the user didn't explicitly mention. Helps assess impact and avoid breaking things.

1,072 161
Explore
davila7/claude-code-templates

verl-rl-training

Provides guidance for training LLMs with reinforcement learning using verl (Volcano Engine RL). Use when implementing RLHF, GRPO, PPO, or other RL algorithms for LLM post-training at scale with flexible infrastructure backends.

23,776 2,298
Explore
davila7/claude-code-templates

openrlhf-training

High-performance RLHF framework with Ray+vLLM acceleration. Use for PPO, GRPO, RLOO, DPO training of large models (7B-70B+). Built on Ray, vLLM, ZeRO-3. 2× faster than DeepSpeedChat with distributed architecture and GPU resource sharing.

23,776 2,298
Explore
davila7/claude-code-templates

gguf-quantization

GGUF format and llama.cpp quantization for efficient CPU/GPU inference. Use when deploying models on consumer hardware, Apple Silicon, or when needing flexible quantization from 2-8 bit without GPU requirements.

23,776 2,298
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results