krishnakanthb13/antigravity_global_skills

daily_log

Scans the current conversation thread and updates a project work log.

View source

How to use

  1. Copy the installation command and review the source package before installing it in your own agent environment.
  2. Check the source document for required tools, credentials and supported hosts.
  3. Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/krishnakanthb13/antigravity_global_skills --skill daily_log

Before you start

  • Installation does not include a model subscription, API allowance or permission to access your files.
  • Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

Daily Log

Use this skill to capture the work done in a session/thread and append it to a persistent log file.

Inputs

  • Scope: The current session context (messages, tools used).
  • Work Log Directory: work_log (default).

Tooling Strategy

  • Use list_dir to find the work_log folder.
  • Use write_to_file to create the new log entry.

Workflow

1. Identify Target

  • Folder: Target the work_log folder in the project's base directory.
  • Context: Scan the current conversation thread to identify:
  • Features implemented.
  • Bugs fixed.
  • Decisions made.

2. Format Entry

Create a markdown entry containing not just what was done, but the context around it:

markdown
## [Date] - [Thread/Topic Name]
-   **Summary**: [One line summary]
-   **Details (The 'What')**:
    -   [Detailed bullet point]
    -   [Detailed bullet point]
-   **Decisions (The 'Why')**:
    -   [Why a specific approach was chosen over alternatives]
-   **Blockers & Open Questions**:
    -   [Any lingering issues or technical debt introduced]
-   **Next Steps**:
    -   [Actionable items for the next session]
-   **Link**: [Markdown Link to Thread/Conversation if available]

3. Save Log Entry

  • Directory: Create or utilize a work_log folder in the project's current working directory.
  • Filename: Add the entry to a unique log file named with the format yyyymmdd-hhmmss.log (e.g., 20260125-005255.log).
  • Action: Use write_to_file to create the new log file within the work_log folder.

4. Output

  • Confirmation: Give explicit confirmation to the user that the log entry has been created and mention the filename and path.
from this repository

More skills

All skills