Run pnpm lint/type-check and create Korean Conventional Commits for fos-blog.
npx skills add https://github.com/jon890/fos-blog --skill commit-and-push-jon890
Please help me install this Agent Skill. Skill: commit-and-push Source: https://github.com/jon890/fos-blog/tree/main/.claude/skills/commit-and-push Command: npx skills add https://github.com/jon890/fos-blog --skill commit-and-push-jon890
Standard workflow for safely committing, pushing, and creating PRs in fos-blog. ALWAYS use this skill when the user says "커밋", "푸시", "올려줘", "반영해줘", "PR 만들어줘", "PR 생성", "작업 저장", "commit", "push", "save work", or any git workflow request — even if they don't mention all three steps. Enforces pnpm lint/type-check, Conventional Commits in Korean, and guides through commit → push → PR as a single unified flow.
Tell me the target files to commit and I will execute the full commit → push → PR flow with lint and type-check checks.
High-intent search queries and answers about installing and using this skill.
You can automate the full git commit, push, and pull request workflow together. This skill coordinates the entire lifecycle as a unified flow, applying safety gates and lint checks before pushing your changes.
Yes, you can enforce pnpm lint and type-check before pushing. The workflow applies these safety gates automatically to ensure code quality standards are met prior to committing and pushing changes.
To write Conventional Commits in Korean, this workflow automatically formats your commit messages according to the specification. It guides you through the commit process while enforcing the Korean conventional commit standard.
You can prevent committing secrets and large artifacts by running safety checks before committing. The workflow includes built-in guards that detect and block unintended artifacts and sensitive data exposure during the git lifecycle.
Git workflow automation supports batch approval mode for faster throughput. This optional mode allows you to streamline the commit, push, and pull request process across multiple files without individual confirmation steps.
The best way to handle these updates is through a unified git flow that coordinates commit, push, and PR creation. This workflow applies to typical development scenarios including feature, bugfix, and documentation updates with enforced checks.
BailipaAutomate pre-commit hook setup with Husky, lint-staged, and Prettier.
SantiagoisperMerge pull requests, deploy code changes, and verify production readiness.
shenjingnanAutomate type checks, linting, and tests after code modifications.
paultyngAutomate Git pre-commit checks, changelog generation, and GitHub pull request updates.
