jhste-skills 0.5.0 → 0.5.2

package/CHANGELOG.md

@@ -2,6 +2,17 @@
 
 ## Unreleased
 
+## 0.5.2 - 2026-07-12
+
+### Changed
+- Updated installation examples to use the current `.agents/skills` locations for user-wide and repository-scoped skills.
+- Clarified when `jhste-coding` should not trigger and required relevant non-destructive validation after code changes.
+
+## 0.5.1 - 2026-07-10
+
+### Changed
+- Refined final-response guidance to report validation and material caveats without generic brevity instructions.
+
 ## 0.5.0 - 2026-07-02
 
 ### Changed

package/README.en.md

@@ -10,25 +10,34 @@ This repository provides one skill:
 
 It does not vendor workflow skills. Use `mattpocock/skills` separately for broader planning, issue, PRD, debugging, architecture, or review workflows.
 
-## Install from npm
+## Install user-wide from npm
 
 This package does not provide a CLI. The npm package is a small distribution bundle for the skill file.
 
 ```sh
 npm install -g jhste-skills
-mkdir -p ~/.codex/skills
-cp -R "$(npm root -g)/jhste-skills/skills/jhste-coding" ~/.codex/skills/
+mkdir -p "$HOME/.agents/skills"
+cp -R "$(npm root -g)/jhste-skills/skills/jhste-coding" "$HOME/.agents/skills/"
 ```
 
-If your agent uses a different skills directory, copy `skills/jhste-coding/` there instead.
+After updating the npm package, run the copy command again to refresh the installed skill.
 
-## Install from the repository
+## Install user-wide from the repository
 
 ```sh
-mkdir -p ~/.codex/skills
-cp -R skills/jhste-coding ~/.codex/skills/
+mkdir -p "$HOME/.agents/skills"
+cp -R skills/jhste-coding "$HOME/.agents/skills/"
 ```
 
+For repository-scoped use, copy the skill from this checkout into the target repository's `.agents/skills` directory.
+
+```sh
+mkdir -p /path/to/target-repo/.agents/skills
+cp -R skills/jhste-coding /path/to/target-repo/.agents/skills/
+```
+
+If another agent expects a different skills directory, copy `skills/jhste-coding/` there instead. Restart Codex if the updated skill does not appear.
+
 ## SOLID-first discipline
 
 `jhste-coding` keeps code changes small and practical, with SOLID as the main lens:

package/README.md

@@ -10,25 +10,34 @@
 
 이 저장소는 workflow 스킬을 vendoring하지 않습니다. 더 넓은 계획, 이슈, PRD, 디버깅, 아키텍처, 리뷰 workflow에는 `mattpocock/skills`를 별도로 사용하세요.
 
-## npm으로 설치
+## npm으로 사용자 전역 설치
 
 이 패키지는 CLI를 제공하지 않습니다. npm 패키지는 스킬 파일을 배포하기 위한 작은 번들입니다.
 
 ```sh
 npm install -g jhste-skills
-mkdir -p ~/.codex/skills
-cp -R "$(npm root -g)/jhste-skills/skills/jhste-coding" ~/.codex/skills/
+mkdir -p "$HOME/.agents/skills"
+cp -R "$(npm root -g)/jhste-skills/skills/jhste-coding" "$HOME/.agents/skills/"
 ```
 
-사용하는 에이전트의 skills 디렉터리가 다르다면 `skills/jhste-coding/`을 그 위치로 복사하세요.
+npm 패키지를 업데이트한 뒤에는 복사 명령을 다시 실행해야 설치된 스킬도 갱신됩니다.
 
-## 저장소에서 설치
+## 저장소에서 사용자 전역 설치
 
 ```sh
-mkdir -p ~/.codex/skills
-cp -R skills/jhste-coding ~/.codex/skills/
+mkdir -p "$HOME/.agents/skills"
+cp -R skills/jhste-coding "$HOME/.agents/skills/"
 ```
 
+특정 저장소에서만 사용하려면 이 저장소를 내려받은 위치에서 대상 저장소의 `.agents/skills`로 복사하세요.
+
+```sh
+mkdir -p /path/to/target-repo/.agents/skills
+cp -R skills/jhste-coding /path/to/target-repo/.agents/skills/
+```
+
+다른 에이전트가 별도 skills 디렉터리를 요구하면 `skills/jhste-coding/`을 그 위치로 복사하세요. Codex가 변경된 스킬을 표시하지 않으면 다시 시작하세요.
+
 ## SOLID-first 규율
 
 `jhste-coding`은 작은 실제 코드 변경에 SOLID를 주된 렌즈로 적용합니다.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "jhste-skills",
-  "version": "0.5.0",
+  "version": "0.5.2",
   "description": "A single lightweight SOLID-first coding discipline skill.",
   "type": "module",
   "license": "MIT",

package/skills/jhste-coding/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: jhste-coding
-description: Apply lightweight SOLID-first coding discipline while actively writing or editing repository code.
+description: Use for implementation, bug fixes, and refactors that modify repository code with lightweight SOLID-first discipline. Do not use for read-only review, planning, architecture discussion, or documentation-only work.
 ---
 
 # jhste-coding
@@ -29,8 +29,9 @@ Use SOLID for the current change; speculative architecture, broad refactors, and
 - Validate external input where it enters the code path.
 - Make uncertain, partial, and failed states visible rather than silently treating them as success.
 - Keep secrets, tokens, credentials, cookies, authorization headers, sessions, and raw sensitive payloads out of logs and responses.
+- After changing code, run the narrowest relevant non-destructive validation. If it cannot run, state why; do not imply the change is verified.
 - When adding or changing tests, focus on observable behavior related to the change.
 
 ## Final response
 
-Briefly say what changed.
+Report what changed, what validation ran, and any material caveat; omit unchanged details and generic background.