https://github.com/junerdd/skills
Reusable AI agent skills for Codex and compatible local runtimes
https://github.com/junerdd/skills
agent-skill ai-agents codex developer-tools prompt-engineering skills
Last synced: about 2 months ago
JSON representation
Reusable AI agent skills for Codex and compatible local runtimes
- Host: GitHub
- URL: https://github.com/junerdd/skills
- Owner: JUNERDD
- License: mit
- Created: 2026-03-09T17:06:23.000Z (4 months ago)
- Default Branch: main
- Last Pushed: 2026-05-10T16:34:42.000Z (about 2 months ago)
- Last Synced: 2026-05-10T17:26:57.868Z (about 2 months ago)
- Topics: agent-skill, ai-agents, codex, developer-tools, prompt-engineering, skills
- Language: Python
- Homepage: https://junerdd-skills.vercel.app
- Size: 2.32 MB
- Stars: 2
- Watchers: 0
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- License: LICENSE
Awesome Lists containing this project
README
# JUNERDD Skills
Reusable AI agent skills published from a single repository.
Current collection version: [`0.1.8`](./VERSION). Release notes are tracked in [`CHANGELOG.md`](./CHANGELOG.md) and published through GitHub Releases.
This repository is a skill collection, not a single-skill package. Installable skills live under [`skills/`](./skills/), and each subfolder is meant to be independently installable and expanded over time. The root [`VERSION`](./VERSION) file tracks the published version of the collection as a whole using SemVer; Git tags and GitHub Releases use the `vX.Y.Z` form. Individual tools or subpackages may keep their own runtime versions when needed.
Stable production URL: [https://junerdd-skills.vercel.app](https://junerdd-skills.vercel.app)
## Website (Vercel)
The companion landing page is a Next.js app in [`web/`](./web/).
English is served from unprefixed paths such as `/` and `/skills/`;
Chinese is served from `/zh-CN` and `/zh-CN/skills/`.
1. In the [Vercel dashboard](https://vercel.com/new), import this GitHub repository.
2. Under **Configure Project**, set **Root Directory** to **`web`** (critical for this monorepo layout).
3. Add **Environment Variable** on **Production**: **`NEXT_PUBLIC_SITE_URL`** = your production domain (example: `https://skills.example.com`, no trailing slash). This should match the **primary Production domain** configured under **Project → Settings → Domains** so Open Graph, canonical URLs, `sitemap.xml`, and `robots.txt` stay consistent.
4. After the first successful Production deployment, open your GitHub repo **Settings → General** and set **Website** to that same production URL so the repository “About” box links to the live site.
## 🧭 Skills At A Glance
If you are deciding what to install, start here:
- [`comment-strategist`](#comment-strategist) - add high-value code comments without comment noise
- [`exhaustive-code-slimmer`](#exhaustive-code-slimmer) - exhaustively reduce maintained code with AST-first evidence
- [`git-commit`](#git-commit) - draft a Conventional Commit message from the staged diff
- [`split-commits`](#split-commits) - split a mixed working tree into focused local commits
- [`multitask-coordinator`](#multitask-coordinator) - coordinate complex subagent work with clear ownership boundaries
- [`debug`](#debug) - debug runtime issues with an evidence-first logging workflow
- [`hack-review`](#hack-review) - review whether an implementation relies on brittle hack-like shortcuts
- [`receiving-hack-review`](#receiving-hack-review) - consume a hack-review report and verify each finding before changing code
- [`regression-review`](#regression-review) - review code changes for user-visible behavioral regressions
- [`receiving-regression-review`](#receiving-regression-review) - consume a regression-review report and verify each finding before changing code
- [`react-wide-api-review`](#react-wide-api-review) - audit excessive React and TypeScript API field flow
- [`receiving-react-wide-api-review`](#receiving-react-wide-api-review) - consume a React wide API review and resolve every item with evidence
## 📦 Install
If you want an agent to install this repository for you without copying files, tell it:
```text
Fetch and follow instructions from https://raw.githubusercontent.com/JUNERDD/skills/refs/heads/main/docs/INSTALL.md
```
If the agent already has this repository open locally, it can read [`./docs/INSTALL.md`](./docs/INSTALL.md) directly instead of fetching the raw GitHub URL.
The CLI examples below intentionally use the latest `skills` tool version to avoid mismatches with older local installs.
List the skills currently published from this repository:
```bash
npx skills@latest add JUNERDD/skills --list
```
Install a specific skill:
```bash
npx skills@latest add JUNERDD/skills --skill
```
Install globally for Codex:
```bash
npx skills@latest add JUNERDD/skills --skill -g -a codex -y
```
Examples:
```bash
npx skills@latest add JUNERDD/skills --skill debug
npx skills@latest add JUNERDD/skills --skill git-commit
npx skills@latest add JUNERDD/skills --skill split-commits
npx skills@latest add JUNERDD/skills --skill multitask-coordinator
npx skills@latest add JUNERDD/skills --skill comment-strategist
npx skills@latest add JUNERDD/skills --skill exhaustive-code-slimmer
npx skills@latest add JUNERDD/skills --skill hack-review
npx skills@latest add JUNERDD/skills --skill receiving-hack-review
npx skills@latest add JUNERDD/skills --skill regression-review
npx skills@latest add JUNERDD/skills --skill receiving-regression-review
npx skills@latest add JUNERDD/skills --skill react-wide-api-review
npx skills@latest add JUNERDD/skills --skill receiving-react-wide-api-review
```
Manual symlink install still works if you prefer not to use the agent prompt:
```bash
mkdir -p ~/.agents/skills
ln -s "$PWD/skills" ~/.agents/skills/junerdd-skill
```
## 🧱 Repository Model
- The collection version lives in the root [`VERSION`](./VERSION) file.
- Release notes live in [`CHANGELOG.md`](./CHANGELOG.md), and published GitHub releases should use matching `vX.Y.Z` tags.
- Use the release workflow to prepare a collection release. It opens a release PR that updates `VERSION`, the README version line, website version metadata, and `CHANGELOG.md` from one workflow input; merging that PR publishes the matching GitHub Release.
- Each installable skill lives under `skills//`.
- Each skill owns its own `SKILL.md` plus any optional `agents/`, `references/`, `scripts/`, or `assets/` directories.
- Root-level files describe the repository as a collection. Skill-specific behavior and deep operational details stay inside the relevant skill folder.
- Shared repository assets such as screenshots can live outside `skills/` when they are not part of the installable package itself.
## 🗂️ Current Skills
Use the anchor list above for a quick jump, then read the section that matches your task.
### `comment-strategist`
[`skills/comment-strategist/`](./skills/comment-strategist/) is for documenting existing code without adding low-value comment noise. It focuses on intent, contracts, constraints, field meaning, and control-flow rationale instead of rewriting syntax in prose.
Install:
```bash
npx skills@latest add JUNERDD/skills --skill comment-strategist
```
Best for:
- documenting exported functions, interfaces, classes, and config objects
- replacing outdated or redundant comments with durable explanations
- adding guided comments inside complex logic while preserving the local comment style
Key entry points:
- Workflow and guardrails: [`skills/comment-strategist/SKILL.md`](./skills/comment-strategist/SKILL.md)
- Optional runtime metadata: [`skills/comment-strategist/agents/openai.yaml`](./skills/comment-strategist/agents/openai.yaml)
### `exhaustive-code-slimmer`
[`skills/exhaustive-code-slimmer/`](./skills/exhaustive-code-slimmer/) exhaustively searches for behavior-preserving code reductions. It combines AST-first structural evidence, audit scripts, deletion-first candidate search, oracle design, and an approval gate for architecture-level refactors so slimming improves maintainability instead of producing dense or risky code.
Install:
```bash
npx skills@latest add JUNERDD/skills --skill exhaustive-code-slimmer
```
Best for:
- finding removable files, branches, exports, dependencies, wrappers, and duplicate logic
- using AST, language-server, parser, or static-tool evidence before text search for structural deletion claims
- running deletion candidates against a build/test/lint/smoke oracle before accepting changes
- identifying architecture problems that block safe code reduction and presenting DX-oriented options before refactoring
Key entry points:
- Workflow and guardrails: [`skills/exhaustive-code-slimmer/SKILL.md`](./skills/exhaustive-code-slimmer/SKILL.md)
- AST-first candidate generation: [`skills/exhaustive-code-slimmer/references/ast_first_candidate_generation.md`](./skills/exhaustive-code-slimmer/references/ast_first_candidate_generation.md)
- Code-slim audit script: [`skills/exhaustive-code-slimmer/scripts/code_slim_audit.py`](./skills/exhaustive-code-slimmer/scripts/code_slim_audit.py)
- Exhaustive shrink script: [`skills/exhaustive-code-slimmer/scripts/exhaustive_shrink.py`](./skills/exhaustive-code-slimmer/scripts/exhaustive_shrink.py)
- Optional runtime metadata: [`skills/exhaustive-code-slimmer/agents/openai.yaml`](./skills/exhaustive-code-slimmer/agents/openai.yaml)
### `git-commit`
[`skills/git-commit/`](./skills/git-commit/) drafts a Conventional Commit message from the staged diff only. It is intentionally narrow: it reads what is already staged, proposes one accurate message, and does not mutate Git state.
Install:
```bash
npx skills@latest add JUNERDD/skills --skill git-commit
```
Best for:
- generating a clean commit subject from the current index
- checking whether a staged batch is too mixed for one honest commit message
- keeping commit wording grounded in staged files instead of unstaged work
Key entry points:
- Workflow and guardrails: [`skills/git-commit/SKILL.md`](./skills/git-commit/SKILL.md)
- Optional runtime metadata: [`skills/git-commit/agents/openai.yaml`](./skills/git-commit/agents/openai.yaml)
### `split-commits`
[`skills/split-commits/`](./skills/split-commits/) helps break a mixed working tree into a sequence of focused local commits. It stages one logical batch at a time, asks `$git-commit` for a message, and requires explicit confirmation before each `git commit`.
Install:
```bash
npx skills@latest add JUNERDD/skills --skill split-commits
```
Best for:
- separating unrelated concerns in the same working tree
- isolating refactors from behavior changes
- building a short series of reviewable local commits without pushing
Key entry points:
- Workflow and guardrails: [`skills/split-commits/SKILL.md`](./skills/split-commits/SKILL.md)
- Optional runtime metadata: [`skills/split-commits/agents/openai.yaml`](./skills/split-commits/agents/openai.yaml)
### `multitask-coordinator`
[`skills/multitask-coordinator/`](./skills/multitask-coordinator/) coordinates non-trivial multi-step work where an agent may use background subagents. It keeps the parent agent responsible for framing, shared contracts, delegation decisions, worker ownership boundaries, synthesis, verification, and user communication.
Install:
```bash
npx skills@latest add JUNERDD/skills --skill multitask-coordinator
```
Best for:
- deciding whether complex repo work should be handled locally or delegated
- assigning disjoint worker scopes in large repositories, monorepos, or dirty worktrees
- keeping shared contracts, package exports, sequencing, and destructive migration boundaries under parent-agent ownership
- synthesizing explorer, implementation, review, or verification results without duplicating work
- preserving parent-agent ownership of final integration, validation, and user-facing status
Key entry points:
- Workflow and guardrails: [`skills/multitask-coordinator/SKILL.md`](./skills/multitask-coordinator/SKILL.md)
- Optional runtime metadata: [`skills/multitask-coordinator/agents/openai.yaml`](./skills/multitask-coordinator/agents/openai.yaml)
### `debug`
[`skills/debug/`](./skills/debug/) provides evidence-first runtime debugging for application bugs, regressions, flaky behavior, and unclear runtime failures. It is the most operational skill in the repository and includes both workflow guidance and a local log collector.
Install:
```bash
npx skills@latest add JUNERDD/skills --skill debug
```
Key entry points:
- Workflow and guardrails: [`skills/debug/SKILL.md`](./skills/debug/SKILL.md)
- Operator reference: [`skills/debug/references/runtime-debugging.md`](./skills/debug/references/runtime-debugging.md)
- Local NDJSON collector: [`skills/debug/scripts/local_log_collector/`](./skills/debug/scripts/local_log_collector/)
- Optional runtime metadata: [`skills/debug/agents/openai.yaml`](./skills/debug/agents/openai.yaml)
### `debug` Skill Snapshot
The `debug` skill is designed to prevent speculative fixes by forcing a prove-it loop:
1. Generate precise hypotheses.
2. Attach to or start an authoritative logging session.
3. Add minimal temporary instrumentation.
4. Reproduce the issue and read the recorded log file.
5. Mark each hypothesis as `CONFIRMED`, `REJECTED`, or `INCONCLUSIVE`.
6. Apply a fix only after the root cause is proven.
7. Verify with fresh post-fix logs before removing instrumentation.
This keeps the skill focused on evidence, not guesswork.
### `debug` Architecture
```mermaid
flowchart LR
User["Developer / Operator"] --> Agent["Agent Runtime"]
Agent --> Skill["debug/SKILL.md
workflow + guardrails"]
Agent --> Ref["runtime-debugging.md
bootstrap + log format"]
Agent --> App["Target app under debug"]
Agent --> Logs["Temporary instrumentation"]
Logs --> Collector["Local NDJSON collector
same-origin dashboard + APIs"]
App --> Logs
Collector --> File["Session log file"]
Collector --> UI["Live dashboard"]
File --> Agent
UI --> Agent
Agent --> Fix["Proven fix + post-fix verification"]
```
### `debug` Highlights
- Evidence-first debugging instead of inspection-only reasoning
- Minimal instrumentation with explicit cleanup after verification
- Per-hypothesis logging and before/after comparison
- Local collector bootstrap when the host does not already provide logging
- Browser-first log transport for frontend debugging, with explicit prohibition on app-local proxy routes unless direct delivery is proven blocked
### `debug` Runtime Support
The current `debug` skill is intentionally portable. It works with:
- OpenAI Codex and similar local-skill runtimes
- Agent shells that read `~/.agents/skills//SKILL.md`
- Custom agent frameworks that mount a skill folder and inject `SKILL.md` into context
- Internal toolchains that want the collector, references, or workflow as reusable assets
If your runtime ignores [`skills/debug/agents/openai.yaml`](./skills/debug/agents/openai.yaml), the core logic is still fully available through [`skills/debug/SKILL.md`](./skills/debug/SKILL.md).
### `debug` Dashboard Preview
### `debug` Collector
The bundled collector is a zero-dependency Python app built on the standard library. It accepts JSON log events, appends them to an NDJSON file, and serves a same-origin dashboard for live inspection.
For frontend and browser debugging, the intended transport is direct client-to-collector HTTP posting. The collector already handles CORS and preflight, so the skill should not create temporary Next.js API routes or other app-local proxy layers unless direct browser delivery has been proven blocked in the current host.
Collector endpoints:
- `POST /ingest`
- `GET /health`
- `GET /api/state`
- `GET /api/logs`
- `GET /api/logs/detail`
- `POST /api/clear`
- `POST /api/shutdown`
Minimal smoke test:
```bash
mkdir -p .debug-logs
python3 skills/debug/scripts/local_log_collector/main.py \
--log-file "$PWD/.debug-logs/demo.ndjson" \
--ready-file "$PWD/.debug-logs/demo.json" \
--session-id "demo-session"
```
### `hack-review`
[`skills/hack-review/`](./skills/hack-review/) reviews whether an implementation is relying on hack-like tactics instead of sound ownership and abstraction boundaries. It produces a coverage-led reviewer report that enumerates all distinct hack-risk findings discovered within scope, records intentional exceptions, and marks uncovered ownership boundaries explicitly.
Install:
```bash
npx skills@latest add JUNERDD/skills --skill hack-review
```
Best for:
- identifying impossible-state fallbacks that hide a broken invariant
- flagging symptom-masking patches that do not fix the root cause
- catching duplicate abstractions or parallel wheels when a stable boundary already exists
- showing which touched ownership boundaries were reviewed, skipped, or left uncovered
Key entry points:
- Workflow and guardrails: [`skills/hack-review/SKILL.md`](./skills/hack-review/SKILL.md)
- Report template: [`skills/hack-review/references/report-template.md`](./skills/hack-review/references/report-template.md)
- Optional runtime metadata: [`skills/hack-review/agents/openai.yaml`](./skills/hack-review/agents/openai.yaml)
### `receiving-hack-review`
[`skills/receiving-hack-review/`](./skills/receiving-hack-review/) consumes a `hack-review` report and builds a disposition ledger for every finding, intentional exception, and open ownership coverage gap before deciding whether to fix, challenge, confirm, or carry it forward.
Install:
```bash
npx skills@latest add JUNERDD/skills --skill receiving-hack-review
```
Best for:
- re-checking that a hack report matches the exact requested review scope
- fixing ownership problems without mechanically deleting necessary guards
- narrowing or disproving hack findings with stronger code-path evidence
- closing or explicitly carrying forward `Not covered` ownership boundaries from the coverage ledger
Key entry points:
- Workflow and guardrails: [`skills/receiving-hack-review/SKILL.md`](./skills/receiving-hack-review/SKILL.md)
- Optional runtime metadata: [`skills/receiving-hack-review/agents/openai.yaml`](./skills/receiving-hack-review/agents/openai.yaml)
### `regression-review`
[`skills/regression-review/`](./skills/regression-review/) reviews whether the current change set introduces user-visible behavioral regressions. It writes a coverage-led reviewer report that enumerates all distinct findings discovered within scope, records intentional visible changes, and marks uncovered surfaces explicitly.
Install:
```bash
npx skills@latest add JUNERDD/skills --skill regression-review
```
Best for:
- checking whether a refactor or feature work breaks user-facing flows
- auditing changed defaults, loading states, retries, ordering, or exported output
- writing a review artifact that keeps severity aligned with the strongest unresolved finding while showing full reviewed coverage
Key entry points:
- Workflow and guardrails: [`skills/regression-review/SKILL.md`](./skills/regression-review/SKILL.md)
- Report template: [`skills/regression-review/references/report-template.md`](./skills/regression-review/references/report-template.md)
- Optional runtime metadata: [`skills/regression-review/agents/openai.yaml`](./skills/regression-review/agents/openai.yaml)
### `receiving-regression-review`
[`skills/receiving-regression-review/`](./skills/receiving-regression-review/) consumes a `regression-review` report and builds a disposition ledger for every finding, intentional visible change, and open coverage gap before deciding whether to fix, challenge, confirm, or carry it forward.
Install:
```bash
npx skills@latest add JUNERDD/skills --skill receiving-regression-review
```
Best for:
- re-checking a regression gate against the current diff and baseline
- fixing only proven user-visible regressions instead of blindly following review comments
- separating real regressions from intentional product deltas with stronger evidence
- closing or explicitly carrying forward `Not covered` user-visible surfaces from the coverage ledger
Key entry points:
- Workflow and guardrails: [`skills/receiving-regression-review/SKILL.md`](./skills/receiving-regression-review/SKILL.md)
- Optional runtime metadata: [`skills/receiving-regression-review/agents/openai.yaml`](./skills/receiving-regression-review/agents/openai.yaml)
### `react-wide-api-review`
[`skills/react-wide-api-review/`](./skills/react-wide-api-review/) performs a scoped, coverage-led audit of oversized React and TypeScript API surfaces. It traces field flow through component props, hooks, contexts, form controllers, table configs, view models, and pass-through chains, then writes a Markdown gate report with findings, intentional exceptions, and coverage ledgers.
Install:
```bash
npx skills@latest add JUNERDD/skills --skill react-wide-api-review
```
Best for:
- finding component props, hook returns, context values, or controller objects that are too wide for their consumers
- tracing pass-through and spread propagation before recommending a narrower owner
- producing an AST-first review report with field-flow and recursive coverage ledgers
Key entry points:
- Workflow and guardrails: [`skills/react-wide-api-review/SKILL.md`](./skills/react-wide-api-review/SKILL.md)
- Report template: [`skills/react-wide-api-review/references/report-template.md`](./skills/react-wide-api-review/references/report-template.md)
- Inventory helper: [`skills/react-wide-api-review/scripts/react_wide_api_inventory.py`](./skills/react-wide-api-review/scripts/react_wide_api_inventory.py)
- Trace helper: [`skills/react-wide-api-review/scripts/react_wide_api_trace.py`](./skills/react-wide-api-review/scripts/react_wide_api_trace.py)
- Optional runtime metadata: [`skills/react-wide-api-review/agents/openai.yaml`](./skills/react-wide-api-review/agents/openai.yaml)
### `receiving-react-wide-api-review`
[`skills/receiving-react-wide-api-review/`](./skills/receiving-react-wide-api-review/) consumes a `react-wide-api-review` report or equivalent PR feedback. It builds a disposition ledger for every finding, intentional exception, field-flow row, and open coverage row before fixing, disproving, narrowing, confirming, or carrying items forward with evidence.
Install:
```bash
npx skills@latest add JUNERDD/skills --skill receiving-react-wide-api-review
```
Best for:
- verifying whether each wide React API finding still applies to the current code
- fixing field ownership, subscription, context, hook return, or pass-through issues without broad rewrites
- preserving Git staging state while reporting a complete disposition for every consumed item
Key entry points:
- Workflow and guardrails: [`skills/receiving-react-wide-api-review/SKILL.md`](./skills/receiving-react-wide-api-review/SKILL.md)
- Disposition template: [`skills/receiving-react-wide-api-review/references/disposition-template.md`](./skills/receiving-react-wide-api-review/references/disposition-template.md)
- Report intake helper: [`skills/receiving-react-wide-api-review/scripts/extract_react_wide_api_report_items.py`](./skills/receiving-react-wide-api-review/scripts/extract_react_wide_api_report_items.py)
- Optional runtime metadata: [`skills/receiving-react-wide-api-review/agents/openai.yaml`](./skills/receiving-react-wide-api-review/agents/openai.yaml)
## 🌱 Growing The Repository
When you add more skills later:
- Create a new folder under `skills//`.
- Keep each skill self-contained so it can be installed independently.
- Add or update `agents/`, `references/`, `scripts/`, and `assets/` only when they materially help that specific skill.
- Update the `Current Skills` section in this README with a one-line summary and relevant links.
- Keep repo-level README content about the collection itself; move deep procedural detail into the skill that owns it.
## 🏗️ Repository Layout
```text
.
├── LICENSE
├── README.md
├── docs/
│ └── images/
│ └── dashboard-overview.png
└── skills/
├── comment-strategist/
│ ├── SKILL.md
│ └── agents/
│ └── openai.yaml
├── debug/
│ ├── SKILL.md
│ ├── agents/
│ │ └── openai.yaml
│ ├── references/
│ │ └── runtime-debugging.md
│ └── scripts/
│ └── local_log_collector/
│ ├── main.py
│ ├── collector_server.py
│ ├── collector_state.py
│ ├── collector_browser.py
│ └── static/
├── exhaustive-code-slimmer/
│ ├── SKILL.md
│ ├── agents/
│ │ └── openai.yaml
│ ├── references/
│ │ ├── ast_first_candidate_generation.md
│ │ ├── code_cleanliness_guide.md
│ │ ├── dx_architecture_gate.md
│ │ ├── language_tactics.md
│ │ ├── oracle_design.md
│ │ ├── research_basis.md
│ │ └── transformation_catalog.md
│ └── scripts/
│ ├── architecture_dx_scan.py
│ ├── code_slim_audit.py
│ └── exhaustive_shrink.py
├── git-commit/
│ ├── SKILL.md
│ └── agents/
│ └── openai.yaml
├── hack-review/
│ ├── SKILL.md
│ ├── agents/
│ │ └── openai.yaml
│ └── references/
│ └── report-template.md
├── multitask-coordinator/
│ ├── SKILL.md
│ └── agents/
│ └── openai.yaml
├── receiving-hack-review/
│ ├── SKILL.md
│ └── agents/
│ └── openai.yaml
├── receiving-react-wide-api-review/
│ ├── SKILL.md
│ ├── agents/
│ │ └── openai.yaml
│ ├── references/
│ │ ├── ast-verification.md
│ │ ├── disposition-template.md
│ │ ├── fix-patterns.md
│ │ ├── report-intake.md
│ │ └── verification.md
│ └── scripts/
│ └── extract_react_wide_api_report_items.py
├── receiving-regression-review/
│ ├── SKILL.md
│ └── agents/
│ └── openai.yaml
├── react-wide-api-review/
│ ├── SKILL.md
│ ├── agents/
│ │ └── openai.yaml
│ ├── references/
│ │ ├── ast-first-analysis.md
│ │ ├── checklist.md
│ │ ├── field-flow-taxonomy.md
│ │ ├── migration.md
│ │ ├── patterns.md
│ │ ├── recursive-audit.md
│ │ ├── report-template.md
│ │ └── scoring-model.md
│ └── scripts/
│ ├── react_wide_api_inventory.py
│ └── react_wide_api_trace.py
├── regression-review/
│ ├── SKILL.md
│ ├── agents/
│ │ └── openai.yaml
│ └── references/
│ └── report-template.md
└── split-commits/
├── SKILL.md
└── agents/
└── openai.yaml
```
## ⚖️ License
Released under the [MIT License](./LICENSE).