atman-33
- 170 skills
- 0 followers
- 4 repo stars
- last month last updated
- ▌ Tdd 3 · atman-33 bundleTest-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.
- ▌ Pr Assistant 3 · atman-33 bundleAnalyzes git changes and assists with creating comprehensive pull requests. Use when user wants to create a PR, review changes before PR, or needs help drafting PR descriptions. Triggers on phrases like 'create PR', 'make a pull request', 'draft PR description', 'what changed in this branch', 'prepare PR'.
- ▌ Write A Skill 2 · atman-33Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill.
- ▌ To Issues 2 · atman-33Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
- ▌ Tdd 2 · atman-33 bundleTest-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
- ▌ Create Pull Request 2 · atman-33 bundleAnalyzes git changes, drafts localized PR titles and bodies, and assists with creating or updating GitHub pull requests for the active agent-harness project repository. Use when working from agent-harness and the user wants to create a PR, review branch changes, draft or update a PR description, or check whether a branch is ready for review.
- ▌ Improve Codebase Architecture 2 · atman-33 bundleScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
- ▌ Openspec Propose 2 · atman-33Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.
- ▌ Ff15 Workspace Project Setup 2 · atman-33 bundleRegister or edit workspace-local FF15 project profiles under .ff15/projects and activate them in .ff15/config/config.yaml. Use when adding or editing a project profile, registering a project in active_projects, diagnosing why a registered project is not resolved for OpenSpec, or validating project profile YAML for the VS Code extension.
- ▌ Ff15 Workspace Operation Customization 2 · atman-33 bundleCreate or diagnose workspace-local FF15 operation files and related facets under .ff15/operations and .ff15/facets. Use when adding or editing custom workspace operations, debugging why a workspace operation is not discoverable or routable, or validating workspace-local YAML and facet references for the VS Code extension.
- ▌ Code Simplifier 2 · atman-33Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Focuses on recently modified code unless instructed otherwise.
- ▌ Openspec Explore 2 · atman-33Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
- ▌ Openspec Onboard 2 · atman-33Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.
- ▌ Openspec Ff Change 2 · atman-33Fast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually.
- ▌ Openspec New Change 2 · atman-33Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.
- ▌ Openspec Sync Specs 2 · atman-33Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.
- ▌ Openspec Apply Change 2 · atman-33Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
- ▌ Openspec Verify Change 2 · atman-33Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.
- ▌ Openspec Archive Change 2 · atman-33Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
- ▌ Obsidian Plugin Deploy 2 · atman-33 bundleBuild and deploy Obsidian plugins to Windows test vault from WSL or Windows environment. Use when working on Obsidian plugin development and need to test changes in the actual Obsidian application. Handles npm build, file copying to vault paths, and creates plugin directory structure automatically. Cross-platform support for WSL and native Windows.
- ▌ Openspec Continue Change 2 · atman-33Continue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow.
- ▌ Obsidian Plugin Release 2 · atman-33 bundleAutomate Obsidian plugin release workflows including version management, CHANGELOG updates, building, PR creation, and GitHub Release publishing. Use when preparing initial releases or version updates for Obsidian community plugins. Handles version consistency across manifest.json, package.json, and versions.json with support for interactive workflows and individual utility scripts.
- ▌ Openspec Bulk Archive Change 2 · atman-33Archive multiple completed changes at once. Use when archiving several parallel changes.
- ▌
- ▌ Kb Init 2 · atman-33Initialize PARA Knowledge Base in your Obsidian vault. Creates index files, log, and adds KB rules to AGENTS.md. Run this first before using other kb- skills.
- ▌ Kb Lint 2 · atman-33Health check for the PARA Knowledge Base. Detects orphan documents, broken links, index drift, tag issues, and stale content. Run periodically or as part of weekly review.
- ▌ Kb Index 2 · atman-33Update Knowledge Base indexes. Smart mode detects changes and updates only what's needed. Full rebuild available with --full flag. Use after adding/moving documents or when indexes feel stale.
- ▌ Kb Query 2 · atman-33Query the PARA Knowledge Base to find information, synthesize answers from multiple documents, and optionally save insights. Use when asking questions about vault content or needing cross-document analysis.
- ▌ Kb Ingest 2 · atman-33Ingest documents into the PARA Knowledge Base. Classifies, moves, links, and indexes new documents from Inbox or a specified path. Use when new documents need processing into the vault.
- ▌ Setup All 2 · atman-33Run all engineering plugin setup steps in sequence — install recommended skills, set up OpenSpec, scaffold project-context.json, and set up rules-ex infrastructure.
- ▌ Create Adr 2 · atman-33Record an architecture/design decision as an ADR (Architecture Decision Record) in the target repository's docs/adr/. Use when the user wants to document a design decision, its alternatives and consequences, or says "record this decision" / "write an ADR".
- ▌ Capture Rule 2 · atman-33Capture a reusable, non-obvious project insight into the rules home where it will auto-inject in future sessions. Use when investigation or implementation surfaces knowledge worth persisting (a gotcha, a convention, the "why" behind a decision), or when the user asks to remember a project learning.
- ▌ Setup Openspec 2 · atman-33Install OpenSpec CLI (if not already installed) and run openspec init --tools claude to add spec-driven development skills to this project.
- ▌ Setup Rules Ex 2 · atman-33 bundleScaffold the rules-ex extended-rules infrastructure (.claude/rules/rules-ex-authoring.md and .claude/rules-ex/README.md) required by the engineering plugin's inject-extended-rules hook.
- ▌
- ▌ Prepare Release 2 · atman-33Prepares a release by creating a release branch, bumping the version, guiding manual changelog curation from git history, and opening a PR to main. Use when the user wants to cut a release, prepare a release PR, ship a version, mentions "release prep", "prepare release", "cut release", or wants to manually write a changelog instead of auto-generating one.
- ▌ Set Openspec Path 2 · atman-33Switch the openspecPath in .claude/project-context.json by picking one of the registered projects from a menu, instead of hand-editing the absolute path.
- ▌ Create Review Guide 2 · atman-33 bundleGenerate a self-contained HTML code-review guide for the current changes — big-picture overview, architecture diagram of affected modules, a file/class responsibility map, and an annotated change walkthrough — so a reviewer can grasp the whole implementation before diving into the diff. Use when the user wants review material for a branch/PR, asks to "explain the changes for review", or wants a visual summary of what was implemented where.
- ▌ Create Feature Branch 2 · atman-33Creates a new feature branch from main inside the intended repository after confirming the branch target and repository context. Use when the user wants to start a new feature branch, asks to create a branch for upcoming work, mentions a branch name such as feature/<name>, or another workflow has already resolved the target repository.
- ▌ Develop Small Feature 2 · atman-33Implement a small, well-scoped feature or fix end-to-end from spec to PR — reuse or create a feature branch, implement test-first, run static checks, get user verification, commit, then open a PR to main.
- ▌ Setup Project Context 2 · atman-33Scaffold or show the .claude/project-context.json file that the engineering hooks read to inject project context, target-repo guidance, and optional post-edit format commands.
- ▌ Investigate Bug Report 2 · atman-33Investigate a reported bug to its root cause — reproduce, trace the code path, identify the defect with evidence, assess blast radius, and propose fix candidates without changing code. Use when the user reports or pastes a bug/defect/unexpected behavior and wants it diagnosed, or asks "why is X happening".
- ▌ Create Onboarding Guide 2 · atman-33 bundleGenerate a self-contained HTML onboarding tour of a repository — architecture diagram, directory map, key flow walkthroughs, and a recommended reading order — for new team members. Use when the user wants onboarding material, asks for a codebase overview/architecture tour, or wants to explain a repo to someone new.
- ▌ Create Manual Test Guide 2 · atman-33 bundleGenerate a self-contained HTML manual-testing guide for an implemented change — environment setup, a visual test-flow diagram, step-by-step scenarios with expected results, and interactive pass/fail checkboxes with a Markdown results export. Use when the user wants to verify an implementation by hand, asks "how do I test this", or wants a verification document for a feature/branch/PR.
- ▌ Install Recommended Skills 2 · atman-33Install recommended engineering skills (improve-codebase-architecture, tdd, to-issues, to-prd, codebase-design, grill-with-docs) via gh skill install.
- ▌ Openspec Propose · atman-33Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.
- ▌ Openspec New Change · atman-33Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.
- ▌ Openspec Sync Specs · atman-33Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.
- ▌ Openspec Verify Change · atman-33Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.
- ▌ Openspec Archive Change · atman-33Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
- ▌ Openspec Continue Change · atman-33Continue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow.
- ▌ Openspec Bulk Archive Change · atman-33Archive multiple completed changes at once. Use when archiving several parallel changes.
- ▌ Openspec Explore · atman-33Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
- ▌ Openspec Apply Change · atman-33Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
- ▌ Pr Assistant 2 · atman-33 bundleAnalyzes git changes, drafts localized PR titles and bodies, and assists with creating comprehensive pull requests. Use when user wants to create a PR, review changes before PR, or needs help drafting PR descriptions. Triggers on phrases like 'create PR', 'make a pull request', 'draft PR description', 'what changed in this branch', 'prepare PR'.
- ▌ Github Release 2 · atman-33 bundleAutomate GitHub release workflows including version management, CHANGELOG updates, PR creation, and GitHub Release publishing for multi-agent-ff15.
- ▌ Operation Customization 2 · atman-33 bundleCreate or customize repository operations and facet files. Use when adding or editing builtin or project-authored workflow YAML, jobs, instructions, skills, policies, or output-contracts, or when diagnosing operation routing, prompt composition, instruction placeholders such as output, setting, or root placeholders, source-aware operation refs, and debug-preview behavior.
- ▌ Agent Relationships 2 · atman-33Noctis、Gladiolus、Ignis、Prompto など FF15 由来 agent の関係性と特徴を短く参照したいときに使う。
- ▌ Operation System Contract 2 · atman-33runtime-owned dispatch、source-aware operationRef、step-completion transport、prompt composition boundary、または live と debug の prompt 差分を変更するときに読むこと。
- ▌ Operation Authoring And Diagnostics 2 · atman-33operation YAML、project workflow authoring path、source-aware operationRef、facet source 解決、output contract、output placeholder、または workflow 関連テストを安全に変更するときに読むこと。
- ▌ Codebase Design · atman-33 bundleShared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
- ▌
- ▌ Ff15 Openspec Agents Sync · atman-33 bundleFF15インスパイアのOpenSpecワークフロー用GitHub Copilotエージェント。Noctis(オーケストレーター + OpenSpec作成)、Iris(Issue管理)、Gladiolus(実装)、Prompto(コード品質)、Ignis(ドキュメント + アーカイブ)、Lunafreya(PR作成)を含むチーム。
- ▌ Init Risk Knowledge · atman-33 bundleInitialize the risk knowledge base repository by removing sample data and creating a clean structure. Use when setting up this repository for a new project. Creates .examples/ directory with sample files for reference while cleaning the main structure. This is a one-time operation for initial project setup.
- ▌ Manage Risk Knowledge · atman-33 bundleManage the risk knowledge base repository for Copilot-driven risk assessment. Use when adding new domains (features), recording incidents, updating risks, or modifying the knowledge-map index. Triggers on requests like "add domain", "record incident", "add risk", "update knowledge-map", or any task involving domains/, incidents/, common-risks/, or indexes/knowledge-map.yml.
- ▌ Obsidian Plugin Deploy · atman-33 bundleBuild and deploy Obsidian plugins to Windows test vault from WSL or Windows environment. Use when working on Obsidian plugin development and need to test changes in the actual Obsidian application. Handles npm build, file copying to vault paths, and creates plugin directory structure automatically. Cross-platform support for WSL and native Windows.
- ▌ Obsidian Plugin Release · atman-33 bundleAutomate Obsidian plugin release workflows including version management, CHANGELOG updates, building, PR creation, and GitHub Release publishing. Use when preparing initial releases or version updates for Obsidian community plugins. Handles version consistency across manifest.json, package.json, and versions.json with support for interactive workflows and individual utility scripts.
- ▌ Kb Init · atman-33Initialize PARA Knowledge Base in your Obsidian vault. Creates index files, log, and adds KB rules to AGENTS.md. Run this first before using other kb- skills.
- ▌ Kb Lint · atman-33Health check for the PARA Knowledge Base. Detects orphan documents, broken links, index drift, tag issues, and stale content. Run periodically or as part of weekly review.
- ▌ Kb Index · atman-33Update Knowledge Base indexes. Smart mode detects changes and updates only what's needed. Full rebuild available with --full flag. Use after adding/moving documents or when indexes feel stale.
- ▌ Kb Query · atman-33Query the PARA Knowledge Base to find information, synthesize answers from multiple documents, and optionally save insights. Use when asking questions about vault content or needing cross-document analysis.
- ▌ Kb Ingest · atman-33Ingest documents into the PARA Knowledge Base. Classifies, moves, links, and indexes new documents from Inbox or a specified path. Use when new documents need processing into the vault.
- ▌ Release · atman-33Runs the full GitHub Actions release pipeline for this extension: triggers version-bump, creates the PR (GITHUB_TOKEN workaround), waits for merge, then dispatches the release workflow. Use when the user wants to release, publish, ship a version, bump the version, or says "バージョンアップ", "リリース", "release minor/major/patch".
- ▌ Workspace Operation Customization · atman-33 bundleCreate or diagnose workspace-local FF15 operation files and related facets under .ff15/operations and .ff15/facets. Use when adding or editing custom workspace operations, debugging why a workspace operation is not discoverable or routable, or validating workspace-local YAML and facet references for the VS Code extension.
- ▌ Ff15 Workspace Project Setup · atman-33 bundleRegister or edit workspace-local FF15 project profiles under .ff15/projects and activate them in .ff15/config/config.yaml. Use when adding or editing a project profile, registering a project in active_projects, diagnosing why a registered project is not resolved for OpenSpec, or validating project profile YAML for the VS Code extension.
- ▌ Ff15 Workspace Operation Customization · atman-33 bundleCreate or diagnose workspace-local FF15 operation files and related facets under .ff15/operations and .ff15/facets. Use when adding or editing custom workspace operations, debugging why a workspace operation is not discoverable or routable, or validating workspace-local YAML and facet references for the VS Code extension.
- ▌ To Prd · atman-33Turn the current conversation into a PRD and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.
- ▌ To Issues · atman-33Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices.
- ▌ Setup All · atman-33Run all engineering plugin setup steps in sequence — install recommended skills, set up OpenSpec, scaffold project-context.json, and set up rules-ex infrastructure.
- ▌ Create Adr · atman-33Record an architecture/design decision as an ADR (Architecture Decision Record) in the target repository's docs/adr/. Use when the user wants to document a design decision, its alternatives and consequences, or says "record this decision" / "write an ADR".
- ▌ Capture Rule · atman-33Capture a reusable, non-obvious project insight into the rules home where it will auto-inject in future sessions. Use when investigation or implementation surfaces knowledge worth persisting (a gotcha, a convention, the "why" behind a decision), or when the user asks to remember a project learning.
- ▌ Setup Openspec · atman-33Install OpenSpec CLI (if not already installed) and run openspec init --tools claude to add spec-driven development skills to this project.
- ▌ Setup Rules Ex · atman-33 bundleScaffold the rules-ex extended-rules infrastructure (.claude/rules/rules-ex-authoring.md and .claude/rules-ex/README.md) required by the engineering plugin's inject-extended-rules hook.
- ▌ Prepare Release · atman-33Prepares a release by creating a release branch, bumping the version, guiding manual changelog curation from git history, and opening a PR to main. Use when the user wants to cut a release, prepare a release PR, ship a version, mentions "release prep", "prepare release", "cut release", or wants to manually write a changelog instead of auto-generating one.
- ▌ Set Openspec Path · atman-33Switch the openspecPath in .claude/project-context.json by picking one of the registered projects from a menu, instead of hand-editing the absolute path.
- ▌ Create Review Guide · atman-33 bundleGenerate a self-contained HTML code-review guide for the current changes — big-picture overview, architecture diagram of affected modules, a file/class responsibility map, and an annotated change walkthrough — so a reviewer can grasp the whole implementation before diving into the diff. Use when the user wants review material for a branch/PR, asks to "explain the changes for review", or wants a visual summary of what was implemented where.
- ▌ Create Feature Branch · atman-33Creates a new feature branch from main inside the intended repository after confirming the branch target and repository context. Use when the user wants to start a new feature branch, asks to create a branch for upcoming work, mentions a branch name such as feature/<name>, or another workflow has already resolved the target repository.
- ▌ Develop Small Feature · atman-33Implement a small, well-scoped feature or fix end-to-end from spec to PR — reuse or create a feature branch, implement test-first, run static checks, get user verification, commit, then open a PR to main.
- ▌ Setup Project Context · atman-33Scaffold or show the .claude/project-context.json file that the engineering hooks read to inject project context, target-repo guidance, and optional post-edit format commands.
- ▌ Investigate Bug Report · atman-33Investigate a reported bug to its root cause — reproduce, trace the code path, identify the defect with evidence, assess blast radius, and propose fix candidates without changing code. Use when the user reports or pastes a bug/defect/unexpected behavior and wants it diagnosed, or asks "why is X happening".
- ▌ Create Onboarding Guide · atman-33 bundleGenerate a self-contained HTML onboarding tour of a repository — architecture diagram, directory map, key flow walkthroughs, and a recommended reading order — for new team members. Use when the user wants onboarding material, asks for a codebase overview/architecture tour, or wants to explain a repo to someone new.
- ▌ Create Manual Test Guide · atman-33 bundleGenerate a self-contained HTML manual-testing guide for an implemented change — environment setup, a visual test-flow diagram, step-by-step scenarios with expected results, and interactive pass/fail checkboxes with a Markdown results export. Use when the user wants to verify an implementation by hand, asks "how do I test this", or wants a verification document for a feature/branch/PR.
- ▌ Agent Memory · atman-33 bundleUse this skill when the user asks to save, remember, recall, or organize memories. Triggers on phrases like 'remember this', 'save this', 'note this', 'what did we discuss about...', 'check your notes', 'clean up memories'. Also use proactively when discovering valuable findings worth preserving.
- ▌ Serena Skills · atman-33 bundleStandalone Serena MCP tools for code intelligence - symbol search, file ops, memory, editing, config, workflow helpers, and shell execution without MCP server
- ▌ Skill Creator · atman-33 bundleGuide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Codex's capabilities with specialized knowledge, workflows, or tool integrations.
- ▌ Prompt Engineer · atman-33Expert in designing effective prompts for LLM-powered applications. Masters prompt structure, context management, output formatting, and prompt evaluation. Use when: prompt engineering, system prompt, few-shot, chain of thought, prompt design.
- ▌ Code Investigator · atman-33 bundleInvestigate code to confirm specifications and provide evidence-based reports. Use for questions like 'what does this do?', 'how is this implemented?', 'where is the spec?', 'explain this behavior', or any request requiring code investigation with documented evidence. Also use for bug investigation requiring current specification understanding.
- ▌ Multi Repo Review · atman-33 bundleCross-repository code review for multi-repo web applications. Use when reviewing changes across multiple repositories to detect inconsistencies in API contracts, type definitions, dependencies, or integration points that single-repo reviews might miss. Triggers on phrases like 'review across repositories', 'check multi-repo changes', 'cross-repo code review', or when working with VSCode workspaces containing multiple project folders.
- ▌ Pr To Origin Main · atman-33 bundleCreate a pull request from current development branch to origin/main (not upstream/main). Use when you need to merge a feature branch into the main branch of your fork and want to ensure the PR targets origin/main with English descriptions. Always confirms remote target with user before creation to prevent accidentally creating PRs to upstream repositories.
- ▌ Local Skill Loader · atman-33 bundleLoads (copies) a skill from a local source directory into the current project's skill library (.claude/skills). Use this when the user wants to import or copy a skill from another location on the filesystem.