takazudo/copilot-instructions
skills/copilot-instructions/SKILL.md
Generate or update .github/copilot-instructions.md for GitHub Copilot. Use when: (1) User wants to create Copilot instructions, (2) User asks to update existing Copilot guidelines, (3) User mentions 'copilot instructions', 'copilot guidelines', or 'copilot config'. Explores codebase for tech stack, file conventions, import patterns, code style, testing. Creates actionable instructions with code examples.
$ install --global
skillsauthnpx skillsauth add takazudo/claude-resources copilot-instructionsInstall 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: May 8, 2026, 4:24 AM145.6s1 file scanned
SKILL.md
- name:
- copilot-instructions
- description:
- Generate or update .github/copilot-instructions.md for GitHub Copilot. Use when: (1) User wants to create Copilot instructions, (2) User asks to update existing Copilot guidelines, (3) User mentions 'copilot instructions', 'copilot guidelines', or 'copilot config'. Explores codebase for tech stack, file conventions, import patterns, code style, testing. Creates actionable instructions with code examples.
Generate or update the .github/copilot-instructions.md file for this repository.
Instructions:
- Check if
.github/copilot-instructions.mdexists:
- Use the Read tool to check if the file exists
- If the file does NOT exist:
- Explore the codebase using the Task tool with subagent_type=Explore
- Focus on understanding:
- Tech stack (frameworks, libraries, languages)
- File naming conventions
- Import patterns
- Component/module structure patterns
- Code style (formatting rules, linting config)
- Testing approach
- Key types and data structures
- Common patterns to follow
- Generate a comprehensive
.github/copilot-instructions.mdfile - Write natural language instructions in Markdown format
- Include critical conventions that developers must follow
- Provide code examples for common patterns
- If the file DOES exist:
- Read the existing
.github/copilot-instructions.mdfile - Explore the codebase carefully using the Task tool with subagent_type=Explore
- Identify:
- New patterns or conventions not documented
- Outdated information that needs updating
- Missing important guidelines
- Areas that need better examples
- Update the file with improvements
- Preserve existing good content
- Add new sections for newly discovered patterns
- Remove or update outdated information
- Content Guidelines:
- Use clear, natural language
- Focus on actionable patterns and conventions
- Include code examples liberally
- Highlight critical "must follow" rules
- Reference key files to check for patterns
- Keep instructions concise but comprehensive
- Organize by topic (naming, imports, components, testing, etc.)
- After creating/updating:
- Inform the user about what was created or changed
- Highlight key conventions that were documented
- Suggest reviewing the file before committing
Note: This creates GitHub Copilot custom instructions following the official format documented at https://docs.github.com/en/copilot/how-tos/configure-custom-instructions/add-repository-instructions
Related Skills
takazudo/dev-linkify-cc-resources
development
VerifiedTrustedCommunity
Link Claude Code skill names mentioned in a CodeGrid article (data/{series}/{n}.md) to the author's public claude-resources repo, pinned to the latest commit hash so links don't rot. Use when: (1) user says 'linkify cc resources', 'link the skills', 'link skill names', or invokes /dev-linkify-cc-resources; (2) editing a CodeGrid article that mentions `/commits`, `/pr-complete`, `/skill-creator` or other Claude Code skills and they should point to claude-resources. Only links skills that actually exist in the public repo; skips hypothetical examples and code blocks.
10SKILL.mdUpdated Jun 2, 2026
takazudo/opus-2nd
development
VerifiedTrustedCommunity
Second opinion from Claude Opus on a plan or approach. Use when: (1) Planning phase of /big-plan needs a higher-quality review than /codex-2nd / /gco-2nd / /gcoc-2nd, (2) User says 'opus 2nd' or 'opus opinion', (3) Wanting Anthropic's larger model to critique a plan. Spawns a general-purpose Agent with model: opus that reads the plan file and returns structured feedback. Anthropic quota — not free.
10SKILL.mdUpdated May 29, 2026
takazudo/dev-ai-based-test
tools
VerifiedTrustedCommunity
AI-based testing via subagent + a per-task test-flow skill. Use when the user wants to verify something that mechanical assertions can't fully capture — image recognition, visual size/position comparison, animation smoothness, multi-step manual flows that need AI judgment. Triggers: 'AI-based test', 'AI test', 'visual verify', 'image recognition test', 'manual operation test', 'human-eye check', 'verify visually', 'compare screenshots', 'looks the same', 'looks correct'. The skill's job is to (1) author a focused test-flow skill that captures the exact procedure + verdict criteria, then (2) dispatch a verification subagent via the Agent tool that loads BOTH the test-flow skill AND a browser-driving skill (/verify-ui primary, /headless-browser fallback) so the subagent has clear context and consistent verdicts. NEVER uses `claude -p` — subagent dispatch goes through the Agent tool exclusively.
10SKILL.mdUpdated May 29, 2026
takazudo/cleanup-resources
development
VerifiedTrustedCommunity
End-of-workflow audit of touched GitHub issues, PRs, and branches via a Sonnet subagent. Use when: (1) /big-plan, /x-as-pr, or /x-wt-teams finishes its main work and needs to verify every touched resource is in the right state (closed when done, kept when ongoing, deleted when dead), (2) User says 'cleanup resources', 'audit cleanup', or 'check what should be closed', (3) A long workflow ends and the manager wants a structured paper trail of what it closed/kept/deleted. Auto-execute by default — the Sonnet agent proposes, the manager (you) executes safe actions and prints a final report.
10SKILL.mdUpdated May 29, 2026