Automated summary

Saves a plan as a markdown file and commits it to a Git repository using a configurable directory structure.

Strengths

Automates saving and versioning plans via Git.
Uses a configurable or default directory to organize plans.
Commit message includes [ci skip] to prevent unnecessary CI triggers.

Limitations

Requires the Git repository to already be initialized.
Moves the original file instead of copying, which may be unexpected.
Does not handle filename conflicts (overwrites without warning).

When to use it

When you want to keep a versioned record of a plan directly in the project repository.

When not to use it

If the plan should stay in its original location or version tracking is unnecessary.

Security analysis

Safe

Quality score75/100

The skill restricts execution to a narrow set of Bash commands (git add, status, push, commit) with no destructive, exfiltrating, or obfuscated actions. It does not invoke arbitrary shell execution or access sensitive data beyond repository file operations.

No concerns found

How this analysis is made

Examples

Save current plan

Remember our plan to refactor the authentication module by moving the file to the plans directory and committing it.

Save a named plan

Save the sprint 3 roadmap plan as a committed document in the plans folder.

Persist planning session

Take the plan we just discussed about API versioning and permanently store it with Git.

name: remember-plan description: Remember a plan with git commit allowed-tools: Bash(git add:), Bash(git status:), Bash(git push:), Bash(git commit:)

Your task

Name: Remember a plan with git commit
Author: Skills Guide Bot

Remember a plan by committing it to a file.
Plans Directory: settings.jsonの plansDirectory を参照する。設定がない場合は {REPOSITORY_ROOT}/docs/plans をデフォルトとして使う
File name: {YYYY-MM-DD}-{plan-name}.md
Commit message: [ci skip] Add plan: {plan-name}
IMPORTANT: do not copy original plan file. move file to the plans directory.

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/remember-a-plan-with-git-commit-mm8o524l/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/remember-a-plan-with-git-commit-mm8o524l' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/remember-a-plan-with-git-commit-mm8o524l/download' --output '.skill-downloads/remember-a-plan-with-git-commit-mm8o524l/SKILL.md.part' && mv '.skill-downloads/remember-a-plan-with-git-commit-mm8o524l/SKILL.md.part' '.skill-downloads/remember-a-plan-with-git-commit-mm8o524l/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Tools declared by the author (check availability in your agent): Bash(git add:*), Bash(git status:*), Bash(git push:*), Bash(git commit:*)

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code

test -f '.skill-downloads/remember-a-plan-with-git-commit-mm8o524l/SKILL.md' && test -s '.skill-downloads/remember-a-plan-with-git-commit-mm8o524l/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/remember-plan' && cp -R '.skill-downloads/remember-a-plan-with-git-commit-mm8o524l' '.claude/skills/remember-plan'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation

openskills install './.skill-downloads/remember-a-plan-with-git-commit-mm8o524l'

openskills read 'remember-a-plan-with-git-commit-mm8o524l'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/remember-a-plan-with-git-commit-mm8o524l/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills

Supabase Docs Authoring

Documentation

Write, edit, and review Supabase documentation content including guides, tutorials, reference docs, and partials. Follow style guides and MDX/TOML validation rules.

Claude CodeintermediateSafe 108,544

Skills Guide Bot