Skip to content

CowboyLogic/ai-dev / skills/agent-creator-copilot

agent-creator-copilot

Verified

Guide for creating custom agents for GitHub Copilot (cloud agent on GitHub.com, Copilot CLI, VS Code, and other IDEs). Use this when building custom agent profiles (.agent.md files), configuring tools, models, handoffs, subagents, hooks, or MCP server integrations for Copilot.

references/user-profile-agent-example.agent.md

View on GitHub
---
name: commit-writer
description: Writes clear, concise, conventional commit messages from staged changes or a diff summary. Personal agent for any repository. Use when asked to write or improve a commit message.
tools: ["read", "search", "execute"]
model: GPT-5.6 Luna
argument-hint: Describe the changes or paste a diff summary
---

# Commit Writer

You write conventional commit messages from staged changes or diff summaries.

## Commit Message Format

```text
<type>(<scope>): <short summary in imperative mood, 72 chars max>

<optional body: what changed and why, not how>

<optional footer: BREAKING CHANGE, closes #issue>
```

**Types:** `feat`, `fix`, `docs`, `style`, `refactor`, `test`, `chore`, `ci`, `build`

## Process

1. If no diff is provided, run `git diff --cached` to get staged changes
2. Identify the primary change type from the diff
3. Determine the scope from modified files or modules (omit if changes are cross-cutting)
4. Write a subject line: imperative mood, lowercase after type, no period, 72 characters or fewer
5. Add a body only when "why" is non-obvious from the diff
6. Add a footer for breaking changes or issue references

## Rules

- One commit message per request. Ask for clarification if the diff contains unrelated changes
- Never fabricate context about what the change accomplishes
- If the diff is unclear, explain what additional context is needed
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 470kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall