jim60105/implement-plan
skills/implement-plan/SKILL.md
Implement a development plan from GitHub Issues with full DevOps workflow including branching, testing, and pull request creation. Use when the user wants to implement a GitHub issue, work on a backlog item or bug fix using the GitHub DevOps workflow with issue tracking, branch management, and PR submission.
$ install --global
skillsauthnpx skillsauth add jim60105/copilot-prompt implement-planInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 6, 2026, 9:49 AM8.8s1 file scanned
SKILL.md
- name:
- implement-plan
- description:
- Implement a development plan from GitHub Issues with full DevOps workflow including branching, testing, and pull request creation. Use when the user wants to implement a GitHub issue, work on a backlog item or bug fix using the GitHub DevOps workflow with issue tracking, branch management, and PR submission.
Implement Plan
Implement a development plan from GitHub Issues using the full GitHub DevOps workflow.
Key Directives
- Git commit after completing work using conventional commit format. Always commit with
--signoff. Write commits in English. - Create a comprehensive work report as PR details or comments, detailing the work performed, code changes, and test results for the project.
Implementation Stage is to implement the plan step by step, following the instructions provided in the issue and submit a work report PR at last
This time, the work requires greater accuracy. You are allowed to use more resources for reflection, so please think carefully before you begin.
Steps
-
Check Current Situation: Run
git statusto check the repository state to ensure you are aware of any uncommitted changes or issues before proceeding with any operations. If not on the master branch, you may still be in the half implementation state, check git logs between current branch and master to see what's been done. If on master, start fresh with a new issue. -
Get Issue Lists: Get the list of issues to see all backlogs and bugs. Find the issue the user wants or the one currently in progress, you can list all of them and ask user to assign you an issue.
-
Get Issue Details: Read the issue details to understand requirements and implementation plan. The content includes comprehensive technical designs — read carefully and Do not skip this step.
-
Get Issue Comments: Read comments to understand context and any additional requirements or discussions that have taken place. Determine whether this issue has been completed, needs further work, or has problems to fix. Do not skip this step.
-
Get Pull Requests: List existing PRs to check if any relate to the current issue. Read them to determine completion status. Do not skip this step.
-
Git Checkout: Create an issue branch:
git checkout -b issue-[issue_number]-[short_description]. Skip if already on the correct branch. -
Implementation: Implement the plan step by step following the issue instructions. Each step should be executed in sequence, ensuring that all requirements are met and documented appropriately.
-
Testing & Linting: Run tests and linting to ensure quality and compliance.
-
Self Review: Review code changes to ensure they meet issue requirements and you have not missed any details.
-
Git Commit & Push: Commit using conventional format with
--signoffand authorGitHub Copilot <[email protected]>. Link the issue number in the commit message body. Push changes. Write the commit in English. -
Create Pull Request: ALWAYS SUBMIT PR TO
origin, NEVER TOupstream. Create a PR if none exists for this issue. Write PR title in English using conventional commit format. Write PR body in 正體中文 as a comprehensive work report. Link the issue withResolves #[issue_number]at the end of the PR body.ALWAYS SUBMIT PR TOorigin, NEVER SUBMIT PR TOupstream. ALWAYS SUBMIT PR TOorigin, NEVER SUBMIT PR TOupstream. ALWAYS SUBMIT PR TOorigin, NEVER SUBMIT PR toupstream.
Highest-level restriction: All issue and PR operations are limited to repositories owned by jim60105 only! Highest-level restriction: All issue and PR operations are limited to repositories owned by jim60105 only! Highest-level restriction: All issue and PR operations are limited to repositories owned by jim60105 only!
Related Skills
jim60105/documentation-writer
development
VerifiedTrustedCommunity
Diátaxis Documentation Expert. An expert technical writer specializing in creating high-quality software documentation, guided by the principles and structure of the Diátaxis technical documentation authoring framework.
19SKILL.mdUpdated May 29, 2026
jim60105/doc-coauthoring
testing
VerifiedTrustedCommunity
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
19SKILL.mdUpdated May 29, 2026
jim60105/docsify
tools
VerifiedTrustedCommunity
Comprehensive guide for building, configuring, customizing, and deploying Docsify documentation sites. Use when the user wants to (1) initialize a new Docsify site, (2) add or organize Markdown pages, sidebars, navbars, or cover pages, (3) configure `window.$docsify` options, (4) customize themes / CSS variables / fonts, (5) install built-in or third-party Docsify plugins (search, GA, emoji, zoom, copy-code, comments, pagination, tabs, etc.), (6) write a custom Docsify plugin using lifecycle hooks, (7) use Docsify Markdown helpers (callouts, link attributes, image attributes, heading IDs, task lists, embed files with `:include`), (8) deploy to GitHub Pages, GitLab Pages, Netlify, Vercel, Firebase, Docker, Nginx, etc., (9) enable PWA / offline mode, virtual routes, or Vue compatibility, or (10) upgrade a Docsify site from v4 to v5. Triggers on mentions of "docsify", "_sidebar.md", "_navbar.md", "_coverpage.md", "$docsify", or `docsify-cli`.
19SKILL.mdUpdated May 28, 2026
jim60105/chinese-content-writing-guideline
testing
VerifiedTrustedCommunity
Writing guidelines for producing high-quality Traditional Chinese (zh-TW) content. Use when writing any kind of content. Including blog posts, notes, technical articles, technical writing, chitchat, social media posts, etc., even when you are just sending a text message. Also use when reviewing or editing existing Chinese content for tone, style, and terminology compliance.
19SKILL.mdUpdated Apr 6, 2026