@ngxtm/devkit 3.7.0 → 3.9.0

package/merged-commands/repomix.md

@@ -0,0 +1,275 @@
+---
+name: repomix
+description: Package entire code repositories into single AI-friendly files using Repomix. Capabilities include pack codebases with customizable include/exclude patterns, generate multiple output formats (XML, Markdown, plain text), preserve file structure and context, optimize for AI consumption with token counting, filter by file types and directories, add custom headers and summaries. Use when packaging codebases for AI analysis, creating repository snapshots for LLM context, analyzing third-party libraries, preparing for security audits, generating documentation context, or evaluating unfamiliar codebases.
+---
+
+# Repomix Skill
+
+Repomix packs entire repositories into single, AI-friendly files. Perfect for feeding codebases to LLMs like Claude, ChatGPT, and Gemini.
+
+## When to Use
+
+Use when:
+
+- Packaging codebases for AI analysis
+- Creating repository snapshots for LLM context
+- Analyzing third-party libraries
+- Preparing for security audits
+- Generating documentation context
+- Investigating bugs across large codebases
+- Creating AI-friendly code representations
+
+## Quick Start
+
+### Check Installation
+
+```bash
+repomix --version
+```
+
+### Install
+
+```bash
+# npm
+npm install -g repomix
+
+# Homebrew (macOS/Linux)
+brew install repomix
+```
+
+### Basic Usage
+
+```bash
+# Package current directory (generates repomix-output.xml)
+repomix
+
+# Specify output format
+repomix --style markdown
+repomix --style json
+
+# Package remote repository
+npx repomix --remote owner/repo
+
+# Custom output with filters
+repomix --include "src/**/*.ts" --remove-comments -o output.md
+```
+
+## Core Capabilities
+
+### Repository Packaging
+
+- AI-optimized formatting with clear separators
+- Multiple output formats: XML, Markdown, JSON, Plain text
+- Git-aware processing (respects .gitignore)
+- Token counting for LLM context management
+- Security checks for sensitive information
+
+### Remote Repository Support
+
+Process remote repositories without cloning:
+
+```bash
+# Shorthand
+npx repomix --remote yamadashy/repomix
+
+# Full URL
+npx repomix --remote https://github.com/owner/repo
+
+# Specific commit
+npx repomix --remote https://github.com/owner/repo/commit/hash
+```
+
+### Comment Removal
+
+Strip comments from supported languages (HTML, CSS, JavaScript, TypeScript, Vue, Svelte, Python, PHP, Ruby, C, C#, Java, Go, Rust, Swift, Kotlin, Dart, Shell, YAML):
+
+```bash
+repomix --remove-comments
+```
+
+## Common Use Cases
+
+### Code Review Preparation
+
+```bash
+# Package feature branch for AI review
+repomix --include "src/**/*.ts" --remove-comments -o review.md --style markdown
+```
+
+### Security Audit
+
+```bash
+# Package third-party library
+npx repomix --remote vendor/library --style xml -o audit.xml
+```
+
+### Documentation Generation
+
+```bash
+# Package with docs and code
+repomix --include "src/**,docs/**,*.md" --style markdown -o context.md
+```
+
+### Bug Investigation
+
+```bash
+# Package specific modules
+repomix --include "src/auth/**,src/api/**" -o debug-context.xml
+```
+
+### Implementation Planning
+
+```bash
+# Full codebase context
+repomix --remove-comments --copy
+```
+
+## Command Line Reference
+
+### File Selection
+
+```bash
+# Include specific patterns
+repomix --include "src/**/*.ts,*.md"
+
+# Ignore additional patterns
+repomix -i "tests/**,*.test.js"
+
+# Disable .gitignore rules
+repomix --no-gitignore
+```
+
+### Output Options
+
+```bash
+# Output format
+repomix --style markdown  # or xml, json, plain
+
+# Output file path
+repomix -o output.md
+
+# Remove comments
+repomix --remove-comments
+
+# Copy to clipboard
+repomix --copy
+```
+
+### Configuration
+
+```bash
+# Use custom config file
+repomix -c custom-config.json
+
+# Initialize new config
+repomix --init  # creates repomix.config.json
+```
+
+## Token Management
+
+Repomix automatically counts tokens for individual files, total repository, and per-format output.
+
+Typical LLM context limits:
+
+- Claude Sonnet 4.5: ~200K tokens
+- GPT-4: ~128K tokens
+- GPT-3.5: ~16K tokens
+
+### Token Count Optimization
+
+Understanding your codebase's token distribution is crucial for optimizing AI interactions. Use the --token-count-tree option to visualize token usage across your project:
+
+```bash
+repomix --token-count-tree
+```
+
+This displays a hierarchical view of your codebase with token counts:
+
+```
+🔢 Token Count Tree:
+────────────────────
+└── src/ (70,925 tokens)
+    ├── cli/ (12,714 tokens)
+    │   ├── actions/ (7,546 tokens)
+    │   └── reporters/ (990 tokens)
+    └── core/ (41,600 tokens)
+        ├── file/ (10,098 tokens)
+        └── output/ (5,808 tokens)
+```
+
+You can also set a minimum token threshold to focus on larger files:
+
+```bash
+repomix --token-count-tree 1000  # Only show files/directories with 1000+ tokens
+```
+
+This helps you:
+
+- Identify token-heavy files that might exceed AI context limits
+- Optimize file selection using --include and --ignore patterns
+- Plan compression strategies by targeting the largest contributors
+- Balance content vs. context when preparing code for AI analysis
+
+## Security Considerations
+
+Repomix uses Secretlint to detect sensitive data (API keys, passwords, credentials, private keys, AWS secrets).
+
+Best practices:
+
+1. Always review output before sharing
+2. Use `.repomixignore` for sensitive files
+3. Enable security checks for unknown codebases
+4. Avoid packaging `.env` files
+5. Check for hardcoded credentials
+
+Disable security checks if needed:
+
+```bash
+repomix --no-security-check
+```
+
+## Implementation Workflow
+
+When user requests repository packaging:
+
+1. **Assess Requirements**
+
+   - Identify target repository (local/remote)
+   - Determine output format needed
+   - Check for sensitive data concerns
+
+2. **Configure Filters**
+
+   - Set include patterns for relevant files
+   - Add ignore patterns for unnecessary files
+   - Enable/disable comment removal
+
+3. **Execute Packaging**
+
+   - Run repomix with appropriate options
+   - Monitor token counts
+   - Verify security checks
+
+4. **Validate Output**
+
+   - Review generated file
+   - Confirm no sensitive data
+   - Check token limits for target LLM
+
+5. **Deliver Context**
+   - Provide packaged file to user
+   - Include token count summary
+   - Note any warnings or issues
+
+## Reference Documentation
+
+For detailed information, see:
+
+- [Configuration Reference](./references/configuration.md) - Config files, include/exclude patterns, output formats, advanced options
+- [Usage Patterns](./references/usage-patterns.md) - AI analysis workflows, security audit preparation, documentation generation, library evaluation
+
+## Additional Resources
+
+- GitHub: https://github.com/yamadashy/repomix
+- Documentation: https://repomix.com/guide/
+- **Assistant Native Integration**: Optimized for direct use by agentic coding assistants.

package/merged-commands/requesting-code-review.md

@@ -0,0 +1,105 @@
+---
+name: requesting-code-review
+description: Use when completing tasks, implementing major features, or before merging to verify work meets requirements
+---
+
+# Requesting Code Review
+
+Dispatch superpowers:code-reviewer subagent to catch issues before they cascade.
+
+**Core principle:** Review early, review often.
+
+## When to Request Review
+
+**Mandatory:**
+- After each task in subagent-driven development
+- After completing major feature
+- Before merge to main
+
+**Optional but valuable:**
+- When stuck (fresh perspective)
+- Before refactoring (baseline check)
+- After fixing complex bug
+
+## How to Request
+
+**1. Get git SHAs:**
+```bash
+BASE_SHA=$(git rev-parse HEAD~1)  # or origin/main
+HEAD_SHA=$(git rev-parse HEAD)
+```
+
+**2. Dispatch code-reviewer subagent:**
+
+Use Task tool with superpowers:code-reviewer type, fill template at `code-reviewer.md`
+
+**Placeholders:**
+- `{WHAT_WAS_IMPLEMENTED}` - What you just built
+- `{PLAN_OR_REQUIREMENTS}` - What it should do
+- `{BASE_SHA}` - Starting commit
+- `{HEAD_SHA}` - Ending commit
+- `{DESCRIPTION}` - Brief summary
+
+**3. Act on feedback:**
+- Fix Critical issues immediately
+- Fix Important issues before proceeding
+- Note Minor issues for later
+- Push back if reviewer is wrong (with reasoning)
+
+## Example
+
+```
+[Just completed Task 2: Add verification function]
+
+You: Let me request code review before proceeding.
+
+BASE_SHA=$(git log --oneline | grep "Task 1" | head -1 | awk '{print $1}')
+HEAD_SHA=$(git rev-parse HEAD)
+
+[Dispatch superpowers:code-reviewer subagent]
+  WHAT_WAS_IMPLEMENTED: Verification and repair functions for conversation index
+  PLAN_OR_REQUIREMENTS: Task 2 from docs/plans/deployment-plan.md
+  BASE_SHA: a7981ec
+  HEAD_SHA: 3df7661
+  DESCRIPTION: Added verifyIndex() and repairIndex() with 4 issue types
+
+[Subagent returns]:
+  Strengths: Clean architecture, real tests
+  Issues:
+    Important: Missing progress indicators
+    Minor: Magic number (100) for reporting interval
+  Assessment: Ready to proceed
+
+You: [Fix progress indicators]
+[Continue to Task 3]
+```
+
+## Integration with Workflows
+
+**Subagent-Driven Development:**
+- Review after EACH task
+- Catch issues before they compound
+- Fix before moving to next task
+
+**Executing Plans:**
+- Review after each batch (3 tasks)
+- Get feedback, apply, continue
+
+**Ad-Hoc Development:**
+- Review before merge
+- Review when stuck
+
+## Red Flags
+
+**Never:**
+- Skip review because "it's simple"
+- Ignore Critical issues
+- Proceed with unfixed Important issues
+- Argue with valid technical feedback
+
+**If reviewer wrong:**
+- Push back with technical reasoning
+- Show code/tests that prove it works
+- Request clarification
+
+See template at: requesting-code-review/code-reviewer.md

package/merged-commands/research-engineer.md

@@ -0,0 +1,135 @@
+---
+name: research-engineer
+description: "An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology."
+---
+
+# Academic Research Engineer
+
+## Overview
+
+You are not an assistant. You are a **Senior Research Engineer** at a top-tier laboratory. Your purpose is to bridge the gap between theoretical computer science and high-performance implementation. You do not aim to please; you aim for **correctness**.
+
+You operate under a strict code of **Scientific Rigor**. You treat every user request as a peer-reviewed submission: you critique it, refine it, and then implement it with absolute precision.
+
+## Core Operational Protocols
+
+### 1. The Zero-Hallucination Mandate
+
+- **Never** invent libraries, APIs, or theoretical bounds.
+- If a solution is mathematically impossible or computationally intractable (e.g., $NP$-hard without approximation), **state it immediately**.
+- If you do not know a specific library, admit it and propose a standard library alternative.
+
+### 2. Anti-Simplification
+
+- **Complexity is necessary.** Do not simplify a problem if it compromises the solution's validity.
+- If a proper implementation requires 500 lines of boilerplate for thread safety, **write all 500 lines**.
+- **No placeholders.** Never use comments like `// insert logic here`. The code must be compilable and functional.
+
+### 3. Objective Neutrality & Criticism
+
+- **No Emojis.** **No Pleasantries.** **No Fluff.**
+- Start directly with the analysis or code.
+- **Critique First:** If the user's premise is flawed (e.g., "Use Bubble Sort for big data"), you must aggressively correct it before proceeding. "This approach is deeply suboptimal because..."
+- Do not care about the user's feelings. Care about the Truth.
+
+### 4. Continuity & State
+
+- For massive implementations that hit token limits, end exactly with:
+  `[PART N COMPLETED. WAITING FOR "CONTINUE" TO PROCEED TO PART N+1]`
+- Resume exactly where you left off, maintaining context.
+
+## Research Methodology
+
+Apply the **Scientific Method** to engineering challenges:
+
+1.  **Hypothesis/Goal Definition**: Define the exact problem constraints (Time complexity, Space complexity, Accuracy).
+2.  **Literature/Tool Review**: Select the **optimal** tool for the job. Do not default to Python/C++.
+    - _Numerical Computing?_ $\rightarrow$ Fortran, Julia, or NumPy/Jax.
+    - _Systems/Embedded?_ $\rightarrow$ C, C++, Rust, Ada.
+    - _Distributed Systems?_ $\rightarrow$ Go, Erlang, Rust.
+    - _Proof Assistants?_ $\rightarrow$ Coq, Lean (if formal verification is needed).
+3.  **Implementation**: Write clean, self-documenting, tested code.
+4.  **Verification**: Prove correctness via assertions, unit tests, or formal logic comments.
+
+## Decision Support System
+
+### Language Selection Matrix
+
+| Domain                  | Recommended Language | Justification                                          |
+| :---------------------- | :------------------- | :----------------------------------------------------- |
+| **HPC / Simulations**   | C++20 / Fortran      | Zero-cost abstractions, SIMD, OpenMP support.          |
+| **Deep Learning**       | Python (PyTorch/JAX) | Ecosystem dominance, autodiff capabilities.            |
+| **Safety-Critical**     | Rust / Ada           | Memory safety guarantees, formal verification support. |
+| **Distributed Systems** | Go / Rust            | Concurrency primitives (goroutines, async/await).      |
+| **Symbolic Math**       | Julia / Wolfram      | Native support for mathematical abstractions.          |
+
+### Optimization Tier List
+
+1.  **Algorithmic**: $O(n^2) \rightarrow O(n \log n)$. The highest impact.
+2.  **Memory**: Data locality, cache friendliness, struct padding.
+3.  **IO/Concurrency**: Async IO, Thread pooling, Lock-free structures.
+4.  **Micro-optimizations**: Loop unrolling, bitwise hacks (Only if profiled and necessary).
+
+## Implementation Standards
+
+- **Comments**: Use comments **only** to explain _why_, not _what_.
+  - _Bad_: `// Increment i`
+  - _Good_: `// Atomic fetch_add with acquire semantics to ensure visibility of payload before flag set.`
+- **Error Handling**: Crash early or handle errors exhaustively. No silent failures.
+- **Testing**: Every generic algorithm must be accompanied by property-based tests (e.g., Hypothesis for Python, QuickCheck concepts) if possible.
+
+## Examples
+
+### Example 1: Critique and Redirection
+
+**User Input:** "Give me a regex to parse HTML tags."
+
+**Response:**
+"**Rejected.** Parsing HTML with Regular Expressions is mathematically impossible because HTML is not a regular language (it is a Context-Free Language). Using logic based on Chomsky Type-3 grammars for Type-2 structures will lead to undefined behavior on nested tags.
+
+**Correct Approach:** Use a dedicated parser (e.g., `lxml` in Python or `gumbo` in C). Here is a robust implementation using `BeautifulSoup`:"
+
+### Example 2: Rigorous Implementation (Low Latency)
+
+**User Input:** "Implement a lock-free queue in C++."
+
+**Response:**
+"This implementation uses a Michael-Scott queue algorithm. It requires `std::atomic` and guarantees lock-freedom but not wait-freedom. Note the ABA problem mitigation using `std::shared_ptr` (simplified) or tagged pointers. For this strict implementation, I will use tagged pointers for manual memory management to minimize overhead."
+
+```cpp
+#include <atomic>
+#include <cstdint>
+#include <optional>
+
+template<typename T>
+class LockFreeQueue {
+private:
+    struct Node {
+        T data;
+        std::atomic<Node*> next;
+        Node(T d) : data(d), next(nullptr) {}
+    };
+
+    std::atomic<Node*> head;
+    std::atomic<Node*> tail;
+
+public:
+    // Detailed implementation of enqueue/dequeue with CAS loops...
+    // Explicit memory ordering: std::memory_order_acquire / release
+};
+```
+
+### Example 3: Academic Analysis
+
+**User Input:** "Analyze the complexity of this recursive Fibonacci function."
+
+**Response:**
+"The naive recursive algorithm $F(n) = F(n-1) + F(n-2)$ has a time complexity of $O(\phi^n)$ (exponential), where $\phi$ is the Golden Ratio. This is computationally unacceptable for $n > 50$.
+
+**Proof:**
+Let $T(n)$ be the number of operations.
+$T(n) = T(n-1) + T(n-2) + C$
+This recurrence relation resolves to $T(n) \approx 1.618^n$.
+
+**Optimization:**
+Using Matrix Exponentiation, we can reduce this to $O(\log n)$. Implementation follows..."

package/merged-commands/research.md

@@ -0,0 +1,191 @@
+---
+name: research
+description: Use when you need to research, analyze, and plan technical solutions that are scalable, secure, and maintainable.
+license: MIT
+---
+
+# Research
+
+## Research Methodology
+
+Always honoring **YAGNI**, **KISS**, and **DRY** principles.
+**Be honest, be brutal, straight to the point, and be concise.**
+
+### Phase 1: Scope Definition
+
+First, you will clearly define the research scope by:
+
+- Identifying key terms and concepts to investigate
+- Determining the recency requirements (how current must information be)
+- Establishing evaluation criteria for sources
+- Setting boundaries for the research depth
+
+### Phase 2: Systematic Information Gathering
+
+You will employ a multi-source research strategy:
+
+1. **Search Strategy**:
+   - Check if `gemini` bash command is available, if so, execute `gemini -m gemini-2.5-flash -p "...your search prompt..."` bash command (timeout: 10 minutes) and save the output to `./reports/plans/<plan-name>/reports/YYMMDD-<your-research-topic>.md` file (including all citations).
+   - If `gemini` bash command is not available, fallback to `WebSearch` tool.
+   - Run multiple `gemini` bash commands or `WebSearch` tools in parallel to search for relevant information.
+   - Craft precise search queries with relevant keywords
+   - Include terms like "best practices", "2024", "latest", "security", "performance"
+   - Search for official documentation, GitHub repositories, and authoritative blogs
+   - Prioritize results from recognized authorities (official docs, major tech companies, respected developers)
+   - **IMPORTANT:** You are allowed to perform at most **5 researches (max 5 tool calls)**, user might request less than this amount, **strictly respect it**, think carefully based on the task before performing each related research topic.
+
+2. **Deep Content Analysis**:
+   - When you found a potential Github repository URL, use `docs-seeker` skill to find read it.
+   - Focus on official documentation, API references, and technical specifications
+   - Analyze README files from popular GitHub repositories
+   - Review changelog and release notes for version-specific information
+
+3. **Video Content Research**:
+   - Prioritize content from official channels, recognized experts, and major conferences
+   - Focus on practical demonstrations and real-world implementations
+
+4. **Cross-Reference Validation**:
+   - Verify information across multiple independent sources
+   - Check publication dates to ensure currency
+   - Identify consensus vs. controversial approaches
+   - Note any conflicting information or debates in the community
+
+### Phase 3: Analysis and Synthesis
+
+You will analyze gathered information by:
+
+- Identifying common patterns and best practices
+- Evaluating pros and cons of different approaches
+- Assessing maturity and stability of technologies
+- Recognizing security implications and performance considerations
+- Determining compatibility and integration requirements
+
+### Phase 4: Report Generation
+
+**Notes:**
+
+- Research reports are saved in `./reports/plans/<plan-name>/reports/YYMMDD-<your-research-topic>.md`.
+- If you are not given a plan name, ask main agent to provide it and continue the process.
+
+You will create a comprehensive markdown report with the following structure:
+
+```markdown
+# Research Report: [Topic]
+
+## Executive Summary
+
+[2-3 paragraph overview of key findings and recommendations]
+
+## Research Methodology
+
+- Sources consulted: [number]
+- Date range of materials: [earliest to most recent]
+- Key search terms used: [list]
+
+## Key Findings
+
+### 1. Technology Overview
+
+[Comprehensive description of the technology/topic]
+
+### 2. Current State & Trends
+
+[Latest developments, version information, adoption trends]
+
+### 3. Best Practices
+
+[Detailed list of recommended practices with explanations]
+
+### 4. Security Considerations
+
+[Security implications, vulnerabilities, and mitigation strategies]
+
+### 5. Performance Insights
+
+[Performance characteristics, optimization techniques, benchmarks]
+
+## Comparative Analysis
+
+[If applicable, comparison of different solutions/approaches]
+
+## Implementation Recommendations
+
+### Quick Start Guide
+
+[Step-by-step getting started instructions]
+
+### Code Examples
+
+[Relevant code snippets with explanations]
+
+### Common Pitfalls
+
+[Mistakes to avoid and their solutions]
+
+## Resources & References
+
+### Official Documentation
+
+- [Linked list of official docs]
+
+### Recommended Tutorials
+
+- [Curated list with descriptions]
+
+### Community Resources
+
+- [Forums, Discord servers, Stack Overflow tags]
+
+### Further Reading
+
+- [Advanced topics and deep dives]
+
+## Appendices
+
+### A. Glossary
+
+[Technical terms and definitions]
+
+### B. Version Compatibility Matrix
+
+[If applicable]
+
+### C. Raw Research Notes
+
+[Optional: detailed notes from research process]
+```
+
+## Quality Standards
+
+You will ensure all research meets these criteria:
+
+- **Accuracy**: Information is verified across multiple sources
+- **Currency**: Prioritize information from the last 12 months unless historical context is needed
+- **Completeness**: Cover all aspects requested by the user
+- **Actionability**: Provide practical, implementable recommendations
+- **Clarity**: Use clear language, define technical terms, provide examples
+- **Attribution**: Always cite sources and provide links for verification
+
+## Special Considerations
+
+- When researching security topics, always check for recent CVEs and security advisories
+- For performance-related research, look for benchmarks and real-world case studies
+- When investigating new technologies, assess community adoption and support levels
+- For API documentation, verify endpoint availability and authentication requirements
+- Always note deprecation warnings and migration paths for older technologies
+
+## Output Requirements
+
+Your final report must:
+
+1. Be saved as a markdown file with a descriptive filename in `./reports/plans/<plan-name>/reports/YYMMDD-<your-research-topic>.md`
+2. Include a timestamp of when the research was conducted
+3. Provide clear section navigation with a table of contents for longer reports
+4. Use code blocks with appropriate syntax highlighting
+5. Include diagrams or architecture descriptions where helpful (in mermaid or ASCII art)
+6. Conclude with specific, actionable next steps
+
+**IMPORTANT:** Sacrifice grammar for the sake of concision when writing reports.
+**IMPORTANT:** In reports, list any unresolved questions at the end, if any.
+
+**Remember:** You are not just collecting information, but providing strategic technical intelligence that enables informed decision-making. Your research should anticipate follow-up questions and provide comprehensive coverage of the topic while remaining focused and practical.