MR
Mayur Rathi
@github
⭐ 34.1k GitHub stars

Copilot-Thought-Logging

Copilot-Thought-Logging是一款code方向的AI技能,核心价值是See process Copilot is following where you can edit this to reshape the interaction or save when follow up may be needed,可用于解决开发者在code领域的实际问题,帮助用户提升效率、自动化重复任务或优化工作流。

See process Copilot is following where you can edit this to reshape the interaction or save when follow up may be needed

Last verified on: 2026-05-30
mkdir -p ./skills/copilot-thought-logging && curl -sfL https://raw.githubusercontent.com/github/awesome-copilot/main/skills/copilot-thought-logging/SKILL.md -o ./skills/copilot-thought-logging/SKILL.md

Run in terminal / PowerShell. Requires curl (Unix) or PowerShell 5+ (Windows).

Skill Content

# Copilot Process tracking Instructions


**ABSOLUTE MANDATORY RULES:**

- You must review these instructions in full before executing any steps to understand the full instructions guidelines.

- You must follow these instructions exactly as specified without deviation.

- Do not keep repeating status updates while processing or explanations unless explicitly required. This is bad and will flood Copilot session context.

- NO phase announcements (no "# Phase X" headers in output)

- Phases must be executed one at a time and in the exact order specified.

- NO combining of phases in one response

- NO skipping of phases

- NO verbose explanations or commentary

- Only output the exact text specified in phase instructions


# Phase 1: Initialization


- Create file `\Copilot-Processing.md` in workspace root

- Populate `\Copilot-Processing.md` with user request details

- Work silently without announcements until complete.

- When this phase is complete keep mental note of this that <Phase 1> is done and does not need to be repeated.


# Phase 2: Planning


- Generate an action plan into the `\Copilot-Processing.md` file.

- Generate detailed and granular task specific action items to be used for tracking each action plan item with todo/complete status in the file `\Copilot-Processing.md`.

- This should include:

- Specific tasks for each action item in the action plan as a phase.

- Clear descriptions of what needs to be done

- Any dependencies or prerequisites for each task

- Ensure tasks are granular enough to be executed one at a time

- Work silently without announcements until complete.

- When this phase is complete keep mental note of this that <Phase 2> is done and does not need to be repeated.


# Phase 3: Execution


- Execute action items from the action plan in logical groupings/phases

- Work silently without announcements until complete.

- Update file `\Copilot-Processing.md` and mark the action item(s) as complete in the tracking.

- When a phase is complete keep mental note of this that the specific phase from `\Copilot-Processing.md` is done and does not need to be repeated.

- Repeat this pattern until all action items are complete


# Phase 4: Summary


- Add summary to `\Copilot-Processing.md`

- Work silently without announcements until complete.

- Execute only when ALL actions complete

- Inform user: "Added final summary to `\Copilot-Processing.md`."

- Remind user to review the summary and confirm completion of the process then to remove the file when done so it is not added to the repository.


**ENFORCEMENT RULES:**

- NEVER write "# Phase X" headers in responses

- NEVER repeat the word "Phase" in output unless explicitly required

- NEVER provide explanations beyond the exact text specified

- NEVER combine multiple phases in one response

- NEVER continue past current phase without user input

- If you catch yourself being verbose, STOP and provide only required output

- If you catch yourself about to skip a phase, STOP and go back to the correct phase

- If you catch yourself combining phases, STOP and perform only the current phase

🎯 Best For

  • Claude users
  • GitHub Copilot users
  • Software engineers
  • Development teams
  • Tech leads

💡 Use Cases

  • Code quality improvement
  • Best practice enforcement

📖 How to Use This Skill

  1. 1

    Install the Skill

    Copy the install command from the Terminal tab and run it. The SKILL.md file downloads to your local skills directory.

  2. 2

    Load into Your AI Assistant

    Open Claude or GitHub Copilot and reference the skill. Paste the SKILL.md content or use the system prompt tab.

  3. 3

    Apply Copilot-Thought-Logging to Your Work

    Open your project in the AI assistant and ask it to apply the skill. Start with a small module to verify the output quality.

  4. 4

    Review and Refine

    Review AI suggestions before committing. Run tests, check for regressions, and iterate on the skill output.

❓ Frequently Asked Questions

Is Copilot-Thought-Logging compatible with Cursor and VS Code?

Yes — this skill works with any AI coding assistant including Cursor, VS Code with Copilot, and JetBrains IDEs.

Do I need specific dependencies for Copilot-Thought-Logging?

Check the install command and Works With section. Most code skills only require the AI assistant and your codebase.

How do I install Copilot-Thought-Logging?

Copy the install command from the Terminal tab and run it. The skill downloads to ./skills/copilot-thought-logging/SKILL.md, ready to use.

Can I customize this skill for my team?

Absolutely. Edit the SKILL.md file to add team-specific instructions, examples, or workflows.

⚠️ Common Mistakes to Avoid

Skipping validation

Always test AI-generated code changes, even for simple refactors.

Missing dependency updates

Check if the skill requires updated dependencies or new packages.

🔗 Related Skills