implement-plan
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 <bot@ChenJ.im>. 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!
More from jim60105/copilot-prompt
chinese-content-writing-guideline
>-
234docx
Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.
140pdf
Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.
84rewrite-meeting-audio-transcription
Rewrite raw meeting audio transcriptions into clean, accurate meeting minutes in Traditional Chinese. Use when the user has an unprocessed audio transcription file with recognition errors and needs it cleaned up into proper meeting minutes.
26create-copilot-instructions
Create `AGENTS.md` file for a project. Use when the user wants to set up custom instructions, configure AI coding assistant behavior, or create project-specific coding guidelines for AI agents.
14drawio-diagrams-enhanced
This skill should be used when the user asks to "create a diagram", "draw a flowchart", "make a swimlane diagram", "create WBS", "generate RACI matrix", "build network diagram", "create org chart", or mentions draw.io, diagrams.net, BPMN, UML, Gantt, PERT, or project management diagrams. Integrates with next-ai-draw-io MCP server for real-time diagram creation and editing.
14