fix: issues on postkit skill, repo migration changes, minor docs - #50
Open
Yasirunet wants to merge 1 commit into
Open
fix: issues on postkit skill, repo migration changes, minor docs#50Yasirunet wants to merge 1 commit into
Yasirunet wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
fix: ship PostKit skills via npx skills + migrate repo to postkitstack org
Branch:
fix/skill-path-issue→developmentSummary
npx skills add postkitstack/Postkitpreviously delivered zero PostKit skills and instead offered the repo's own internal contributor tooling, becauseagent/skills/is not a directory the skills CLI searches..claude/skills/workflows asinternalso they are no longer shipped to end users, and fixes two of them that failed YAML parsing.appritechnologies/postkitto the newpostkitstack/Postkitorg.Changes
agent/skills/→skills/: moved all four public skills (postkit-migrate,postkit-setup,postkit-schema,postkit-auth) with zero content changes.skills/is a default discovery location for the skills CLI;agent/skills/is not — it appears in the CLI only as an install destination for deepagents/eve, never as a source. The recursive fallback scan is gated onskills.length === 0, and.claude/skills/was already yielding matches, so the public skills were never reachable..claude/skills/*/SKILL.md(7 files): addedmetadata: internal: true, which the skills CLI honours by excluding the skill from discovery,--list, and interactive install. Claude Code ignores the field, so/bugfix,/create-pretc. keep working locally, and contributors can still fetch them withINSTALL_INTERNAL_SKILLS=1or an explicit--skill <name>..claude/skills/{bugfix,create-feature}/SKILL.md: quoted descriptions containing:— unquoted, YAML parsed them as nested mappings and the CLI skipped both files with a parse error.--all -ycommand inCLAUDE.mdanddocs/docs/agent-skills/overview.mdwith an explicit four---skillform.--allis shorthand for--skill '*' --agent '*' -y, so it both bypasses the internal-skill filter and fans the install out across every supported agent directory.agent-skills/overview.md: the Scope table listed./<agent>/skills/; real project paths are agent-specific (.claude/skills/for Claude Code,.agents/skills/shared by Cursor/Codex/Cline/Gemini CLI/Copilot,.windsurf/skills/,.roo/skills/). Added a "Verify the Install" step usingnpx skills list.Public vs Internal Skillssection inCLAUDE.md: documents the two skill directories, the requiredinternalflag, and the colon-quoting rule. Cross-referenced from "Adding a New Skill" and the Skills Registry, the two places a contributor would otherwise add a skill to the wrong directory.README.md,cli/README.md,cli/package.json,docs/docusaurus.config.ts,docs/src/pages/index.tsx,docs/docs/getting-started/installation.md,docs/docs/modules/db/troubleshooting.md): all GitHub URLs now point topostkitstack/Postkit, normalising the previously inconsistentpostkit/Postkitcasing. Also updatesorganizationName/projectNameand botheditUrls in the Docusaurus config, and correctscd postkit/cli→cd Postkit/cliso the from-source clone instructions work on case-sensitive filesystems.Type of Change
Test Plan
npm run test) — not run; no CLI source touched (changes are skill markdown, docs, and package metadata)npm run test:e2e) (if applicable) — not applicable for the same reasonnpm run build) —docusaurus buildfor the docs site, which is meaningful here becauseonBrokenLinks: 'throw'is set and would fail on any broken cross-linknpx skills@1.5.22 add <repo> --listagainst a snapshot of the branch — returns exactly the fourpostkit-*skills with no warnings (before: 5 internal skills plus 2 YAML parse errors, and none of the public ones). Verified the documented CI command installs exactly those four into.claude/skills/and nothing else; verifiedINSTALL_INTERNAL_SKILLS=1still surfaces all 11 for contributors. Confirmed every documented agent id (claude-code,cursor,codex,cline,gemini-cli,github-copilot,windsurf,roo) and flag (-a,-g,-y,--skill,--agent,--copy,--list) exists in the CLI, and thatnpx skills listis a real subcommand. Checked no staleagent/references remain in CI workflows,.gitignore, or build config.Breaking Changes
Note for reviewers: two related items were deliberately left out of scope —
docs/blog/authors.ymlstill carries theappritechnologiesauthor profile URL andtitle: Appri Technologies(author identity, a branding decision rather than a path move), and the published npm package remains@appritech/postkit(unaffected by the GitHub org move; renaming it is a coordinated npm change).