tech-radar

Name: tech-radar
Author: faizkhairi

61stars19forks

How to install tech-radar?

faizkhairi/claude-code-blueprint/tech-radar

$npx -y skills add faizkhairi/claude-code-blueprint --skill tech-radar

Installs into the current project.

Summary

MUST use when user asks 'what's new?', 'any updates?', 'latest versions?', 'breaking changes?', 'should we upgrade?', 'what changed in X?', or when starting a new project. Detects dependencies dynamically from package.json / requirements.txt / go.mod / composer.json first

Files · 1

View on GitHub

SKILL.md

1	# Tech Radar: Stack Update Scanner
2
3	Checks for latest versions, breaking changes, deprecations, and security advisories across the user's core stack.
4
5	## Core Stack to Monitor
6
7	> Example only, replace with your own stack. The table below reflects one project's dependencies (a JS/TS stack). The skill detects your actual dependencies from the project manifest at runtime (`package.json`, `requirements.txt`, `go.mod`, `composer.json`, etc., see the description); this table is just a fallback of well-known packages to watch.
8
9	\| Category \| Packages \|
10	\|----------\|----------\|
11	\| Frontend \| nuxt, vue, next, react, tailwindcss, formkit, pinia \|
12	\| Backend \| @nestjs/core, express, fastify \|
13	\| Database \| prisma, @prisma/client, knex, better-auth \|
14	\| Testing \| vitest, @vue/test-utils, @testing-library/react \|
15	\| Mobile \| expo, react-native, nativewind \|
16	\| AI \| ai (vercel ai-sdk), @ai-sdk/openai, @ai-sdk/anthropic \|
17	\| CLI \| commander, chalk, ora, inquirer \|
18	\| Build \| typescript, tsup, turbo, vite \|
19	\| Cloud \| @aws-sdk/client-s3, @aws-sdk/client-ec2 \|
20
21	## Execution Steps
22
23	1. Parse arguments: If user specified a package/framework, focus on that. Otherwise scan full stack.
24
25	2. Check latest versions using WebSearch:
26	- Search: `"{package} latest version {current_year}"`
27	- Compare against currently installed version (check the project manifest: `package.json`, `requirements.txt`, `go.mod`, `composer.json`, etc.)
28	- Flag major version bumps (potential breaking changes)
29
30	3. Check for breaking changes:
31	- For major version bumps: search `"{package} v{new_major} migration guide"`
32	- Summarize key breaking changes that affect our patterns
33	- Cross-reference against known patterns in MEMORY.md
34
35	4. Check security advisories:
36	- Search: `"{package} CVE {current_year}"` or `"{package} security advisory"`
37	- Flag any HIGH or CRITICAL severity issues
38
39	5. Check deprecations:
40	- Search: `"{package} deprecated features {current_year}"`
41	- Note any APIs we currently use that are deprecated
42
43	## Output Format
44
45	```
46	## Tech Radar Report — {date}
47
48	### Upgrades Available
49	\| Package \| Current \| Latest \| Breaking? \| Priority \|
50	\|---------\|---------\|--------\|-----------\|----------\|
51	\| nuxt \| 4.0.0 \| 4.1.0 \| No \| Low \|
52	\| prisma \| 6.2.0 \| 7.0.0 \| YES \| High \|
53
54	### Breaking Changes (Action Required)
55	- prisma 7.0: No `url` in datasource block, driver adapter required [details]
56
57	### Security Advisories
58	- (none found / list any CVEs)
59
60	### Deprecation Warnings
61	- (none / list deprecated APIs we use)
62
63	### Recommendation
64	[1-2 sentences: upgrade now / wait / specific actions needed]
65	```
66
67	## Smart Filtering
68
69	- Only report packages actually used in the active project (check the project manifest)
70	- Skip patch/minor version bumps unless they contain security fixes
71	- Prioritize: Security > Breaking Changes > Major Upgrades > Minor Upgrades
72	- If checking all projects: deduplicate (report each package once with all affected projects)

People who liked this also viewed

6 picks

Type

tech-radar

61stars19forks

View on GitHub

How to install tech-radar?

faizkhairi/claude-code-blueprint/tech-radar

$npx -y skills add faizkhairi/claude-code-blueprint --skill tech-radar

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Tech Radar: Stack Update Scanner
2
3	Checks for latest versions, breaking changes, deprecations, and security advisories across the user's core stack.
4
5	## Core Stack to Monitor
6
7	> Example only, replace with your own stack. The table below reflects one project's dependencies (a JS/TS stack). The skill detects your actual dependencies from the project manifest at runtime (`package.json`, `requirements.txt`, `go.mod`, `composer.json`, etc., see the description); this table is just a fallback of well-known packages to watch.
8
9	\| Category \| Packages \|
10	\|----------\|----------\|
11	\| Frontend \| nuxt, vue, next, react, tailwindcss, formkit, pinia \|
12	\| Backend \| @nestjs/core, express, fastify \|
13	\| Database \| prisma, @prisma/client, knex, better-auth \|
14	\| Testing \| vitest, @vue/test-utils, @testing-library/react \|
15	\| Mobile \| expo, react-native, nativewind \|
16	\| AI \| ai (vercel ai-sdk), @ai-sdk/openai, @ai-sdk/anthropic \|
17	\| CLI \| commander, chalk, ora, inquirer \|
18	\| Build \| typescript, tsup, turbo, vite \|
19	\| Cloud \| @aws-sdk/client-s3, @aws-sdk/client-ec2 \|
20
21	## Execution Steps
22
23	1. Parse arguments: If user specified a package/framework, focus on that. Otherwise scan full stack.
24
25	2. Check latest versions using WebSearch:
26	- Search: `"{package} latest version {current_year}"`
27	- Compare against currently installed version (check the project manifest: `package.json`, `requirements.txt`, `go.mod`, `composer.json`, etc.)
28	- Flag major version bumps (potential breaking changes)
29
30	3. Check for breaking changes:
31	- For major version bumps: search `"{package} v{new_major} migration guide"`
32	- Summarize key breaking changes that affect our patterns
33	- Cross-reference against known patterns in MEMORY.md
34
35	4. Check security advisories:
36	- Search: `"{package} CVE {current_year}"` or `"{package} security advisory"`
37	- Flag any HIGH or CRITICAL severity issues
38
39	5. Check deprecations:
40	- Search: `"{package} deprecated features {current_year}"`
41	- Note any APIs we currently use that are deprecated
42
43	## Output Format
44
45	```
46	## Tech Radar Report — {date}
47
48	### Upgrades Available
49	\| Package \| Current \| Latest \| Breaking? \| Priority \|
50	\|---------\|---------\|--------\|-----------\|----------\|
51	\| nuxt \| 4.0.0 \| 4.1.0 \| No \| Low \|
52	\| prisma \| 6.2.0 \| 7.0.0 \| YES \| High \|
53
54	### Breaking Changes (Action Required)
55	- prisma 7.0: No `url` in datasource block, driver adapter required [details]
56
57	### Security Advisories
58	- (none found / list any CVEs)
59
60	### Deprecation Warnings
61	- (none / list deprecated APIs we use)
62
63	### Recommendation
64	[1-2 sentences: upgrade now / wait / specific actions needed]
65	```
66
67	## Smart Filtering
68
69	- Only report packages actually used in the active project (check the project manifest)
70	- Skip patch/minor version bumps unless they contain security fixes
71	- Prioritize: Security > Breaking Changes > Major Upgrades > Minor Upgrades
72	- If checking all projects: deduplicate (report each package once with all affected projects)

People who liked this also viewed

6 picks

Type