Skip to content
cccskills
FreePublished on GitHub

agent-commit

Analyze changes and create a meaningful commit with agent authorship. Internal skill for evolve_loop.

The English summary is being prepared. Showing the original description.

See how to install

Files included (2)

  • SKILL.md3.3 KB
  • source.json600 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

Agent Commit

Creates a git commit with meaningful message based on skill output and actual file changes.

When to Use

This skill is called automatically by evolve_loop.py after a content-modifying skill completes. It is not intended for manual invocation.

Input

You will receive:

  1. The name of the skill that just ran
  2. A summary or excerpt of that skill's output

Instructions

1. Check for Changes

Run git status --porcelain to see if there are uncommitted changes.

If there are no changes, output "No changes to commit" and stop.

2. Analyze the Changes

Run git diff (or git diff --cached if files are staged) to understand what was modified.

Focus on:

  • Which files were changed (especially content files in obsidian/)
  • The nature of the changes (new content, edits, deletions)
  • Key themes or topics affected

3. Generate Commit Message

Create a commit message with a summary line and body:

<type>(<skill>): <summary>

<body>

Summary line (required, under 72 chars):

  • <type> is one of: feat, fix, refine, research, chore
  • <skill> is the skill name (e.g., deep-review, condense, expand-topic)
  • <summary> describes WHAT was done and to WHICH file(s)
  • File paths must include parent directory (e.g., topics/free-will.md not just free-will.md)

Body (required for content changes):

  • 2-5 bullet points summarizing key changes
  • For condense: before/after word counts, what was cut vs preserved
  • For deep-review: what issues were found and fixed
  • For expand-topic: key themes covered
  • For research: sources consulted, main findings

Good examples:

refine(condense): reduce topics/free-will.md from 9567 to 2985 words

- Cut quantum Zeno redundancy (7+ mentions → 1 via link)
- Removed extended sections on altered states, process philosophy
- Preserved core phenomenology arguments and Mary's Room
- Kept tenet connections and cross-links intact
refine(deep-review): improve clarity in concepts/qualia.md

- Fixed circular definition in opening paragraph
- Added concrete examples for inverted spectrum argument
- Strengthened connection to hard problem article

Bad examples:

  • auto(deep-review): Automated execution (too vague, no body)
  • Updated files (no context)
  • refine(condense): reduce free-will.md (missing parent directory - is it topics/ or concepts?)

4. Create the Commit

Stage all changes and commit with agent authorship. Use a HEREDOC for the multi-line message:

git add -A
git commit --author "unfinishablemap.org Agent <agent@unfinishablemap.org>" -m "$(cat <<'EOF'
<summary line>

- bullet point 1
- bullet point 2
EOF
)"

5. Output the Result

Output the commit hash and message so the calling system can log it.

Important

  • Keep commit messages under 72 characters for the summary line
  • Always include parent directory in file paths (e.g., topics/free-will.md, concepts/qualia.md, research/notes.md)
  • Focus on the "what" and "which file" - the skill name already tells us "how"
  • If multiple files changed, mention the primary one and note others exist
  • Never include time estimates or subjective assessments in commit messages

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

007

Free

Security audit, hardening, threat modeling (STRIDE/PASTA), Red/Blue Team, OWASP checks, code review, incident response, and infrastructure security for any project.

The English summary is being prepared. Showing the original description.

aibot88/sec_skill_store5Updated May 27, 2026

Guides the creation of agile user stories and Gherkin feature files. Use when the user wants to create a user story, write acceptance criteria, define Gherkin scenarios, or author BDD feature files. This should trigger for requests such as Create a user story; Write a user story; I need to write a user story. Part of cursor-rules-java project

The English summary is being prepared. Showing the original description.

aibot88/sec_skill_store5Updated May 27, 2026

Facilitates conversational discovery to create Architectural Decision Records (ADRs) for non-functional requirements using the ISO/IEC 25010:2023 quality model. Use when the user wants to document quality attributes, NFR decisions, security/performance/scalability architecture, or design systems with measurable quality criteria. This should trigger for requests such as Create ADR for Non-functional requirements; Document Non-functional requirements; Capture Non-functional requirements; Generate Non-functional requirements in an ADR. Part of cursor-rules-java project

The English summary is being prepared. Showing the original description.

aibot88/sec_skill_store5Updated May 27, 2026

Run a health check on an existing project: dependency audit, security scan, test runner detection, CI/CD evaluation, and missing configuration analysis. Maps the three execution gates (pre/in/post) from /10x-bootstrapper to an assessment framework for existing codebases. Reads optional context/foundation/stack-assessment.md from /10x-stack-assess to focus checks on identified gaps. Writes context/foundation/health-check.md with findings, prioritized fixes, and an agent-readiness verdict. Use when the user has an existing project and wants to verify its health before working with an agent. Trigger phrases: "health check", "check my project", "audit my project", "is my project healthy", "sprawdź projekt", "audyt projektu", "health-check", "project health". Use AFTER /10x-stack-assess (brownfield chain), BEFORE agent onboarding (m1-l4).

The English summary is being prepared. Showing the original description.

aibot88/sec_skill_store5Updated May 27, 2026

You MUST use this when building projects end-to-end. Orchestrates all 12 team roles — automatically switches between CTO, architect, PM, engineers, SRE, security, DBA, QA, and EM based on the current phase of work. Starts with brainstorming before any implementation.

The English summary is being prepared. Showing the original description.

aibot88/sec_skill_store5Updated May 27, 2026

Use when you need to add or configure Maven plugins in your pom.xml — including quality tools (enforcer, surefire, failsafe, jacoco, pitest, spotbugs, pmd), security scanning (OWASP), code formatting (Spotless), version management, container image build (Jib), build information tracking, and benchmarking (JMH) — through a consultative, modular step-by-step approach that only adds what you actually need. This should trigger for requests such as Add Maven plugins in pom.xml; Improve Maven plugins in pom.xml. Part of cursor-rules-java project

The English summary is being prepared. Showing the original description.

aibot88/sec_skill_store5Updated May 27, 2026

See all skills by aibot88

Report a problem with this skill