Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .claude-plugin/marketplace.json
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@
{
"name": "raystack",
"source": "./",
"version": "1.2.0",
"version": "1.2.1",
"description": "Skills by Harun R. Rayhan: a full development flow (new project intake, research, PRD, specs, plans, reviewed builds, ship; gap-fill, design review and migration for existing projects), read-only scans and reviews (security, performance, scalability, reliability and availability, architecture incl. MVC and CQRS, frontend, code health, CI/CD pipelines, AWS, infrastructure, databases), working principles and local browser verification.",
"category": "devops"
}
Expand Down
2 changes: 1 addition & 1 deletion .claude-plugin/plugin.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "raystack",
"version": "1.2.0",
"version": "1.2.1",
"description": "Skills by Harun R. Rayhan: a full development flow (new project intake, research, PRD, specs, plans, reviewed builds, ship; gap-fill, design review and migration for existing projects), read-only scans and reviews (security, performance, scalability, reliability and availability, architecture incl. MVC and CQRS, frontend, code health, CI/CD pipelines, AWS, infrastructure, databases), working principles and local browser verification.",
"author": {
"name": "Harun R. Rayhan",
Expand Down
2 changes: 1 addition & 1 deletion .cursor-plugin/plugin.json
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
{
"name": "raystack",
"displayName": "RayStack",
"version": "1.2.0",
"version": "1.2.1",
"description": "Skills by Harun R. Rayhan: a full development flow (new project intake, research, PRD, specs, plans, reviewed builds, ship; gap-fill, design review and migration for existing projects), read-only scans and reviews (security, performance, scalability, reliability and availability, architecture incl. MVC and CQRS, frontend, code health, CI/CD pipelines, AWS, infrastructure, databases), working principles and local browser verification.",
"author": {
"name": "Harun R. Rayhan"
Expand Down
8 changes: 8 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,13 @@
# Changelog

## 1.2.1 (2026-11-04)

From running `dev-migrate` end to end (a pricing module moved from Express to Go, with the
old code kept until a parity check passed):

- The limits questions (downtime, deadline, data) are asked one at a time. It had asked all
of them in one numbered list.

## 1.2.0 (2026-11-04)

- New `cve-review`: finds known CVEs in dependencies (osv-scanner and the ecosystem audits,
Expand Down
2 changes: 1 addition & 1 deletion VERSION
Original file line number Diff line number Diff line change
@@ -1 +1 @@
1.2.0
1.2.1
4 changes: 2 additions & 2 deletions plugin.json
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
{
"$schema": "https://agent-plugins.org/schemas/1.2.0/plugin.schema.json",
"$schema": "https://agent-plugins.org/schemas/1.2.1/plugin.schema.json",
"name": "raystack",
"version": "1.2.0",
"version": "1.2.1",
"description": "Skills by Harun R. Rayhan: a full development flow (new project intake, research, PRD, specs, plans, reviewed builds, ship; gap-fill, design review and migration for existing projects), read-only scans and reviews (security, performance, scalability, reliability and availability, architecture incl. MVC and CQRS, frontend, code health, CI/CD pipelines, AWS, infrastructure, databases), working principles and local browser verification.",
"author": {
"name": "Harun R. Rayhan",
Expand Down
4 changes: 3 additions & 1 deletion skills/dev-migrate/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,9 @@ is not already clear:
2. **To what?** The target language, framework, database or platform.
3. **Why?** Speed, cost, hiring, safety, a dead dependency. The reason decides what to
measure at the end.
4. **Limits:** downtime allowed, deadline, data that must not be lost or reshaped.
4. **Limits:** downtime allowed, then deadline, then data that must not be lost or reshaped
(skip data when the part has no store). Each is its own question; never one numbered list.
After the last one, ask the deployment shape only if research leaves it open.

Log each answer as a `D-` row.

Expand Down
Loading