feat: add 6 agents + 5 slash commands for full coverage (v2.7.0) (#293)

Phase 3: 6 new agents (all 9 categories covered) + 5 slash commands.
This commit is contained in:
Alireza Rezvani
2026-03-07 12:36:03 +01:00
committed by GitHub
parent 87070d46e9
commit fa07912835
11 changed files with 538 additions and 0 deletions

30
commands/changelog.md Normal file
View File

@@ -0,0 +1,30 @@
---
name: changelog
description: Generate changelogs from git history and validate conventional commits. Usage: /changelog <generate|lint> [options]
---
# /changelog
Generate Keep a Changelog entries from git history and validate commit message format.
## Usage
```
/changelog generate [--from <tag>] [--to HEAD] Generate changelog entries
/changelog lint [--range <from>..<to>] Lint commit messages
```
## Examples
```
/changelog generate --from v2.0.0
/changelog lint --range main..dev
/changelog generate --from v2.0.0 --to v2.1.0 --format markdown
```
## Scripts
- `engineering/changelog-generator/scripts/generate_changelog.py` — Parse commits, render changelog
- `engineering/changelog-generator/scripts/commit_linter.py` — Validate conventional commit format
## Skill Reference
`engineering/changelog-generator/SKILL.md`

View File

@@ -0,0 +1,40 @@
---
name: competitive-matrix
description: Build competitive analysis matrices with scoring and gap analysis. Usage: /competitive-matrix <analyze> [options]
---
# /competitive-matrix
Build competitive matrices with weighted scoring, gap analysis, and market positioning insights.
## Usage
```
/competitive-matrix analyze <competitors.json> Full analysis
/competitive-matrix analyze <competitors.json> --weights pricing=2,ux=1.5 Custom weights
```
## Input Format
```json
{
"your_product": { "name": "MyApp", "scores": {"ux": 8, "pricing": 7, "features": 9} },
"competitors": [
{ "name": "Competitor A", "scores": {"ux": 7, "pricing": 9, "features": 6} }
],
"dimensions": ["ux", "pricing", "features"]
}
```
## Examples
```
/competitive-matrix analyze competitors.json
/competitive-matrix analyze competitors.json --format json --output matrix.json
```
## Scripts
- `product-team/competitive-teardown/scripts/competitive_matrix_builder.py` — Matrix builder
## Skill Reference
`product-team/competitive-teardown/SKILL.md`

30
commands/pipeline.md Normal file
View File

@@ -0,0 +1,30 @@
---
name: pipeline
description: Detect stack and generate CI/CD pipeline configs. Usage: /pipeline <detect|generate> [options]
---
# /pipeline
Detect project stack and generate CI/CD pipeline configurations for GitHub Actions or GitLab CI.
## Usage
```
/pipeline detect [<project-dir>] Detect stack, tools, and services
/pipeline generate [--platform github|gitlab] Generate pipeline YAML
```
## Examples
```
/pipeline detect ./my-project
/pipeline generate --platform github
/pipeline generate --platform gitlab --stages build,test,deploy
```
## Scripts
- `engineering/ci-cd-pipeline-builder/scripts/stack_detector.py` — Detect stack and tooling
- `engineering/ci-cd-pipeline-builder/scripts/pipeline_generator.py` — Generate pipeline YAML
## Skill Reference
`engineering/ci-cd-pipeline-builder/SKILL.md`

32
commands/tdd.md Normal file
View File

@@ -0,0 +1,32 @@
---
name: tdd
description: Generate tests, analyze coverage, and run TDD workflows. Usage: /tdd <generate|coverage|validate> [options]
---
# /tdd
Generate tests, analyze coverage, and validate test quality using the TDD Guide skill.
## Usage
```
/tdd generate <file-or-dir> Generate tests for source files
/tdd coverage <test-dir> Analyze test coverage and gaps
/tdd validate <test-file> Validate test quality (assertions, edge cases)
```
## Examples
```
/tdd generate src/auth/login.ts
/tdd coverage tests/ --threshold 80
/tdd validate tests/auth.test.ts
```
## Scripts
- `engineering-team/tdd-guide/scripts/test_generator.py` — Generate test cases
- `engineering-team/tdd-guide/scripts/coverage_analyzer.py` — Coverage analysis
- `engineering-team/tdd-guide/scripts/test_quality_checker.py` — Quality validation
## Skill Reference
`engineering-team/tdd-guide/SKILL.md`

34
commands/tech-debt.md Normal file
View File

@@ -0,0 +1,34 @@
---
name: tech-debt
description: Score, track, and prioritize technical debt. Usage: /tech-debt <scan|score|report> [options]
---
# /tech-debt
Scan codebases for technical debt, score severity, and generate prioritized remediation plans.
## Usage
```
/tech-debt scan <project-dir> Scan for debt indicators
/tech-debt score <project-dir> Calculate debt score (0-100)
/tech-debt report <project-dir> Full report with remediation plan
```
## Examples
```
/tech-debt scan ./src
/tech-debt score . --format json
/tech-debt report . --output debt-report.md
```
## Scripts
- `engineering/tech-debt-tracker/scripts/debt_scanner.py` — Detect debt patterns
- `engineering/tech-debt-tracker/scripts/debt_scorer.py` — Calculate severity scores
- `engineering/tech-debt-tracker/scripts/remediation_planner.py` — Generate fix plans
- `engineering/tech-debt-tracker/scripts/trend_tracker.py` — Track debt over time
- `engineering/tech-debt-tracker/scripts/cost_estimator.py` — Estimate remediation cost
## Skill Reference
`engineering/tech-debt-tracker/SKILL.md`