Deep analysis of Git history: identify frequently changed hotspot files, analyze code ownership by contributor, and scan for leaked secrets. Triggered when users ask about Git analysis, code hotspots, who owns what code, secret scanning, security audits of commit history, or optimizing code review assignments.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
Perform three-dimensional analysis on a Git repository: hotspot file detection, code ownership analysis, and secret leak scanning.
scripts/hotfiles.sh)Identify the most frequently changed files in a repository to help spot:
Usage:
bash scripts/hotfiles.sh [options]
| Option | Description | Default |
|---|---|---|
--repo PATH | Repository path | Current directory |
--top N | Show top N files | 20 |
--since DATE | Start date (e.g. 2024-01-01) | None |
--until DATE | End date | None |
--author AUTHOR | Filter by author | None |
--format FORMAT | Output format: table / csv / json | table |
scripts/ownership.sh)Analyze actual code ownership, reporting for each contributor within the specified scope:
Usage:
bash scripts/ownership.sh [options]
| Option | Description | Default |
|---|---|---|
--repo PATH | Repository path | Current directory |
--path SUBPATH | Analyze a specific subdirectory or file | Entire repo |
--top N | Show top N contributors | 10 |
--since DATE | Start date | None |
--format FORMAT | Output format: table / csv / json | table |
scripts/secret-scan.sh)Scan the full Git history (including deleted commits) for common secrets and sensitive information:
Usage:
bash scripts/secret-scan.sh [options]
| Option | Description | Default |
|---|---|---|
--repo PATH | Repository path | Current directory |
--branch BRANCH | Scan a specific branch | All branches |
--since DATE | Start date | None |
--format FORMAT | Output format: table / csv / json | table |
--severity LEVEL | Minimum severity level: low / medium / high | low |
git (>= 2.20)bash (>= 4.0)awk, sort, head, grepNo additional dependencies or paid APIs required.
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
Simulates academic peer review, evaluating papers across Originality, Methodology, Results, and Writing to provide Major/Minor Revision recommendations with actionable feedback. Triggers when a user asks to "review my paper," "simulate peer review," or "give my paper a peer review.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill should be used when the user asks to "attack Active Directory", "exploit AD", "Kerberoasting", "DCSync", "pass-the-hash", "BloodHound enumeration", "Golden Ticket", "Silver Ticket", "AS-REP roasting", "NTLM relay", or needs guidance on Windows domain penetration testing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill should be used when the user asks to "test API security", "fuzz APIs", "find IDOR vulnerabilities", "test REST API", "test GraphQL", "API penetration testing", "bug bounty API testing", or needs guidance on API security assessment techniques.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate multiple radically different interface designs for a module using parallel sub-agents. Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Interactive system flow tracing across CODE, API, AUTH, DATA, NETWORK layers with SQLite persistence and Mermaid export. Use for security audits, compliance documentation, flow tracing, feature ideation, brainstorming, debugging, architecture reviews, or incident post-mortems. Triggers on audit, trace flow, document flow, security review, debug flow, brainstorm, architecture review, post-mortem, incident review.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Authentication patterns: session vs JWT vs OAuth comparison, provider selection (NextAuth, Clerk, Supabase Auth), security checklist, and common mistakes. Use when implementing auth, reviewing auth flows, or choosing auth providers.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.