ccc Semantic Code Search
cocoindex-io/cocoindex-code
Semantic code search and index management with the ccc CLI: the agent initializes, indexes and queries the project by concept, filtering by language or path.
Generate coding-aider plans as created by the IntelliJ coding-aider plugin.
Install Coding Aider Plan Generator
$ npx skills add p-wegner/coding-aider --skill coding-aider-plan-generator -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install p-wegner/coding-aider coding-aider-plan-generator --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/p-wegner/coding-aider.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/coding-aider-plan-generator .claude/skills/coding-aider-plan-generator && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "coding-aider-plan-generator" agent skill from https://github.com/p-wegner/coding-aider/tree/main/.claude/skills/coding-aider-plan-generator into .claude/skills/coding-aider-plan-generator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "coding-aider-plan-generator", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/p-wegner/coding-aider/tree/main/.claude/skills/coding-aider-plan-generatorType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add p-wegner/coding-aider --skill coding-aider-plan-generator -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install p-wegner/coding-aider coding-aider-plan-generator --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/p-wegner/coding-aider.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/coding-aider-plan-generator .agents/skills/coding-aider-plan-generator && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "coding-aider-plan-generator" agent skill from https://github.com/p-wegner/coding-aider/tree/main/.claude/skills/coding-aider-plan-generator into .agents/skills/coding-aider-plan-generator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "coding-aider-plan-generator", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add p-wegner/coding-aider --skill coding-aider-plan-generator -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install p-wegner/coding-aider coding-aider-plan-generator --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/p-wegner/coding-aider.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/coding-aider-plan-generator .cursor/skills/coding-aider-plan-generator && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "coding-aider-plan-generator" agent skill from https://github.com/p-wegner/coding-aider/tree/main/.claude/skills/coding-aider-plan-generator into .cursor/skills/coding-aider-plan-generator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "coding-aider-plan-generator", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/p-wegner/coding-aider.git --path .claude/skills/coding-aider-plan-generator--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add p-wegner/coding-aider --skill coding-aider-plan-generator -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install p-wegner/coding-aider coding-aider-plan-generator --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/p-wegner/coding-aider.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/coding-aider-plan-generator .gemini/skills/coding-aider-plan-generator && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "coding-aider-plan-generator" agent skill from https://github.com/p-wegner/coding-aider/tree/main/.claude/skills/coding-aider-plan-generator into .gemini/skills/coding-aider-plan-generator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "coding-aider-plan-generator", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install p-wegner/coding-aider coding-aider-plan-generatorInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add p-wegner/coding-aider --skill coding-aider-plan-generator -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/p-wegner/coding-aider.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/coding-aider-plan-generator .github/skills/coding-aider-plan-generator && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "coding-aider-plan-generator" agent skill from https://github.com/p-wegner/coding-aider/tree/main/.claude/skills/coding-aider-plan-generator into .github/skills/coding-aider-plan-generator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "coding-aider-plan-generator", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add p-wegner/coding-aider --skill coding-aider-plan-generator -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install p-wegner/coding-aider coding-aider-plan-generator --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/p-wegner/coding-aider.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/coding-aider-plan-generator .opencode/skills/coding-aider-plan-generator && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "coding-aider-plan-generator" agent skill from https://github.com/p-wegner/coding-aider/tree/main/.claude/skills/coding-aider-plan-generator into .opencode/skills/coding-aider-plan-generator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "coding-aider-plan-generator", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
coding-aider-plan-generator- GitHub stars
- 105
- Token cost
- ~1.7k tokens
- SKILL.md length
- 661 words
- Files
- 8 (incl. scripts)
- Skills in repo
- 1
- Repo updated
- First seen
- Licence
- GPL-3.0
At a glance
Generate coding-aider plans as created by the IntelliJ coding-aider plugin.
- Works in 8 steps: Plan Structure Analysis → Plan Directory Setup → Main Plan File Generation → …
- User explicitly asks for a coding-aider plan
- SKILL.md covers Overview, When This Skill Activates, Instructions and Examples, plus 2 more sections
- Runs Shell and Python scripts from its folder
What it does
Coding Aider Plan Generator is an agent skill from p-wegner/coding-aider. Generate coding-aider plans as created by the IntelliJ coding-aider plugin. Use when user explicitly asks for a "coding-aider plan", "aider plan", or needs structured development planning with checklist tracking and file context management.
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 9 other files, including scripts (for example `examples.md`, `reference.md` and `scripts/plan-check.sh`).
It sits in Agent Workflows, covering Context engineering. It works with JetBrains IDEs. The licence is GPL-3.0.
When your agent uses it
- User explicitly asks for a coding-aider plan
- Needs structured development planning with checklist tracking and file context management
Example prompts
- “coding-aider plan”
- “aider plan”
- “/coding-aider-plan-generator”
Requirements
- Python 3
- A Bash shell
- Pre-approved tools (allowed-tools): Read, Write, Edit, Grep, Glob, Bash
Workflow steps
8 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit cf6563a. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadWriteEditGrepGlobBash
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 2 files in scripts/ (Shell and Python), which the agent can run.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Coding Aider Plan Generator loads about 1.7k tokens when it runs. Until then it costs about 67 tokens; SKILL.md has 661 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
allowed-tools: Read, Write, Edit, Grep, Glob, Bash
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from p-wegner/coding-aider at commit cf6563a, republished under its GPL-3.0 licence (© p-wegner). 661 words, ~1,747 tokens.
Download SKILL.mdSave it as
.claude/skills/coding-aider-plan-generator/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.- name
- coding-aider-plan-generator
- description
- Generate coding-aider plans as created by the IntelliJ coding-aider plugin. Use when user explicitly asks for a "coding-aider plan", "aider plan", or needs structured development planning with checklist tracking and file context management.
- allowed-tools
- Read, Write, Edit, Grep, Glob, Bash
Coding-Aider Plan Generator
Generate structured coding-aider plans that mirror the IntelliJ coding-aider plugin's plan system, complete with overview, goals, implementation checklist, and file context management.
Overview
This skill creates coding-aider plans in the exact format used by the IntelliJ coding-aider plugin. Plans include structured overviews, problem descriptions, goals, implementation checklists, and file context management for systematic development tracking.
When This Skill Activates
Use this skill when the user explicitly requests:
- "Create a coding-aider plan"
- "Generate an aider plan"
- "I need a coding-aider plan for..."
- "Create a structured development plan like coding-aider"
- Similar explicit requests for coding-aider style planning
Instructions
1. Plan Structure Analysis
First, understand the user's requirements:
- What feature or task needs to be implemented?
- What is the current state or problem?
- What are the specific goals and constraints?
- Which files will likely be involved?
2. Plan Directory Setup
Create the plan storage structure:
- Create
.coding-aider-plans/directory if it doesn't exist - Generate a plan name based on the feature/task (kebab-case)
- Plan files will be stored as:
{plan_name}.md,{plan_name}_checklist.md,{plan_name}_context.yaml
3. Main Plan File Generation
Create the main plan file ({plan_name}.md) with this structure:
# [Coding Aider Plan]
# Plan Title
## Overview
High-level description of the feature to be implemented
## Problem Description
Current issues, challenges, or requirements that necessitate this plan
## Goals
1. Specific, measurable goal 1
2. Specific, measurable goal 2
3. Specific, measurable goal 3
## Additional Notes and Constraints
- Technical constraints or limitations
- Dependencies on other systems or features
- Performance considerations
- Security requirements
- Testing requirements
## References
- Links to relevant documentation
- Related files or components
- External resources or examples4. Checklist File Generation
Create the checklist file ({plan_name}_checklist.md) with atomic implementation tasks:
# [Coding Aider Plan - Checklist]
# Plan Title - Implementation Checklist
- [ ] Analysis and research task
- [ ] Setup/initialization task
- [ ] Core implementation task 1
- [ ] Core implementation task 2
- [ ] Integration task
- [ ] Testing task 1
- [ ] Testing task 2
- [ ] Documentation update
- [ ] Code review/refinement
- [ ] Deployment/finalization5. Context File Generation
Create the context file ({plan_name}_context.yaml) with relevant implementation files:
---
files:
- path: "src/main/kotlin/package/FeatureFile.kt"
readOnly: false
- path: "src/test/kotlin/package/FeatureTest.kt"
readOnly: false
- path: "build.gradle.kts"
readOnly: true6. Content Generation Guidelines
Plan Titles
- Use clear, descriptive titles
- Include the main feature or component name
- Keep titles concise but informative
Goals Section
- Make goals specific and measurable
- Focus on outcomes, not implementation details
- Include 3-5 primary goals maximum
- Each goal should be achievable independently
Checklist Items
- Break down implementation into atomic tasks
- Each item should represent a single, completable action
- Order tasks logically (setup → implementation → testing → documentation)
- Include both development and validation tasks
- Aim for 8-15 checklist items depending on complexity
Context Files
- Include all files that will need modification
- Mark read-only files appropriately (config files, tests to read, etc.)
- Include build files, configuration, and main implementation files
- Group related files by directory/package structure
7. File Context Discovery
To identify relevant files for the context.yaml:
- Use Glob to find files matching the feature area
- Use Grep to search for related functionality
- Include configuration files (build.gradle, pom.xml, etc.)
- Include test files for the feature area
- Include documentation files if relevant
8. Plan Validation
Before completing, verify:
- Plan name is kebab-case and descriptive
- All three files are created with correct naming
- Checklist items are atomic and actionable
- Context files exist and are correctly marked
- Plan structure matches plugin format exactly
Show full SKILL.md (251 more words)Show less
Examples
Example 1: New Feature Plan
User request: "Create a coding-aider plan for implementing user authentication"
Generated plan structure:
user-authentication.md- Main plan with auth overview, goals, security constraintsuser-authentication_checklist.md- Tasks for JWT setup, password hashing, API endpointsuser-authentication_context.yaml- AuthController, UserService, security config files
Example 2: Refactoring Plan
User request: "I need a coding-aider plan for refactoring the payment processing module"
Generated plan structure:
payment-processing-refactor.md- Current issues, refactoring goals, migration strategypayment-processing-refactor_checklist.md- Step-by-step refactoring tasks with testingpayment-processing-refactor_context.yaml- PaymentService, PaymentController, test files
Example 3: Bug Fix Plan
User request: "Create a coding-aider plan for fixing the memory leak in the data processor"
Generated plan structure:
memory-leak-fix.md- Problem description, root cause analysis, fix approachmemory-leak-fix_checklist.md- Debugging, patching, verification tasksmemory-leak-fix_context.yaml- DataProcessor, related memory management files
Requirements
- Current working directory should be a project directory
- Sufficient permissions to create
.coding-aider-plans/directory - Access to project files for context analysis
Troubleshooting
Plan Directory Issues
- If
.coding-aider-plans/cannot be created, check directory permissions - Ensure working in a valid project directory with write access
File Context Discovery
- If no relevant files are found, ask user to specify key files
- Use broader search patterns with Glob if specific searches fail
- Include common project files (build configs, main source directories)
Plan Naming
- Use kebab-case for plan names (convert spaces to hyphens)
- Keep names under 50 characters for readability
- Avoid special characters beyond hyphens
Checklist Quality
- If checklist items are too broad, break them into smaller atomic tasks
- Ensure each item can be completed independently
- Include both development and validation/testing tasks
© p-wegner, GPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 7 other files (scripts) in .claude/skills/coding-aider-plan-generator of p-wegner/coding-aider.
- SKILL.md
- examples.md
- reference.md
- scripts/plan-check.sh
- scripts/validate-plan.py
- templates/checklist-template.md
- templates/context-template.yaml
- templates/plan-template.md
Open the folder on GitHubat commit cf6563a
Compare with similar skills
Coding Aider Plan Generator next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Coding Aider Plan Generator this skillp-wegner/coding-aider | 105 | — | ~1.7k | Automated safety check: Notes | GPL-3.0 | |
| ccc Semantic Code Searchcocoindex-io/cocoindex-code | 2.7k | — | ~938 | Automated safety check: Pass | Apache-2.0 | |
| Repomix Codebase Packeryamadashy/repomix | 29k | — | ~1.3k | Automated safety check: Notes | MIT | |
| MCP Code Search Tool SelectionContext-Engine-AI/Context-Engine | 402 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Repo Context Ledgergviiisen/repo-context-ledger | 105 | — | ~2.8k | Automated safety check: Pass | MIT | |
| Code Context Slicingtrailofbits/skills | 7.4k | — | ~2.1k | Automated safety check: Pass | CC-BY-SA-4.0 |
Similar skills
Repomix Codebase Packer
yamadashy/repomix
Packs a local directory or remote GitHub repository into one AI-friendly file with Repomix, then searches it to explore structure, find patterns and count tokens.
MCP Code Search Tool Selection
Context-Engine-AI/Context-Engine
Rules for choosing Qdrant-Indexer semantic search over grep or file reads when exploring code, debugging or asking where and why questions.
Repo Context Ledger
gviiisen/repo-context-ledger
Record every behavior-changing feature addition, fix, and adjustment as durable, evidence-based repository knowledge, then use that ledger to continue accurately across AI windows, tools, Git…
- Official
Code Context Slicing
trailofbits/skills
Picks a small, graph-based slice of source with Trailmark and hands a focused code task to a smaller or local model without exposing the whole repository.
MoAI Foundation Core
modu-ai/moai-adk
Reference for MoAI-ADK's core development principles: TRUST 5 quality gates, SPEC-first domain-driven workflow, agent delegation and token budgeting.
Related
Works with
Categories
Questions about Coding Aider Plan Generator
What does Coding Aider Plan Generator do?
Generate coding-aider plans as created by the IntelliJ coding-aider plugin. Coding Aider Plan Generator is an agent skill from p-wegner/coding-aider. Generate coding-aider plans as created by the IntelliJ coding-aider plugin.
When should I use Coding Aider Plan Generator?
Coding Aider Plan Generator fits situations like: user explicitly asks for a coding-aider plan; needs structured development planning with checklist tracking and file context management.
How do I install Coding Aider Plan Generator in Claude Code?
Run `npx skills add p-wegner/coding-aider --skill coding-aider-plan-generator -a claude-code`. Or copy the skill folder (.claude/skills/coding-aider-plan-generator in p-wegner/coding-aider) into .claude/skills/coding-aider-plan-generator in your project. Claude Code loads it when a task matches its description.
How do I install Coding Aider Plan Generator in Codex?
Run `npx skills add p-wegner/coding-aider --skill coding-aider-plan-generator -a codex`. Or copy the skill folder (.claude/skills/coding-aider-plan-generator in p-wegner/coding-aider) into .agents/skills/coding-aider-plan-generator in your project. Codex loads it when a task matches its description.
Can I use Coding Aider Plan Generator in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add p-wegner/coding-aider --skill coding-aider-plan-generator -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/coding-aider-plan-generator, .gemini/skills/coding-aider-plan-generator, .github/skills/coding-aider-plan-generator and .opencode/skills/coding-aider-plan-generator in your project.
What does Coding Aider Plan Generator need to run?
Going by SKILL.md and its folder, Coding Aider Plan Generator needs a shell and Python for the scripts in its folder. Our summary lists: Python 3; A Bash shell. Its frontmatter pre-approves these tools: Read, Write, Edit, Grep, Glob, Bash.
Does Coding Aider Plan Generator access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Coding Aider Plan Generator safe to install?
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Coding Aider Plan Generator use?
Coding Aider Plan Generator is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Coding Aider Plan Generator use?
About 1.7k tokens (SKILL.md is roughly 7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Coding Aider Plan Generator?
Skills that share tags, products or a category with Coding Aider Plan Generator: ccc Semantic Code Search (cocoindex-io/cocoindex-code, 2.7k stars), Repomix Codebase Packer (yamadashy/repomix, 29k stars), MCP Code Search Tool Selection (Context-Engine-AI/Context-Engine, 402 stars) and Repo Context Ledger (gviiisen/repo-context-ledger, 105 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Coding Aider Plan Generator?
p-wegner (a GitHub user) maintains it in p-wegner/coding-aider, which has 105 GitHub stars. The repository was last updated on March 30, 2026.
Source: p-wegner/coding-aider on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.