Enhance abstract skill for DITA short descriptions#4814
Conversation
|
The PR preview for e688592 is available at theforeman-foreman-documentation-preview-pr-4814.surge.sh No diff compared to the current base |
|
Going to test it. |
|
TBH, I have no idea if the results are better or worse now... see #4815 (raw AI output, single latest attempt, no manual editing) @aneta-petrova @jafiala Care to try it out too? |
|
This took two attempts and minor manual editing, but I think the result is pretty good: #4822 |
| - For module-type-specific abstract rules, look up the reference file that matches the `:_mod-docs-content-type:` AsciiDoc attribute in the module (open and apply that file in full): | ||
| - `CONCEPT` → [references/concept.md](references/concept.md) | ||
| - `PROCEDURE` → [references/procedure.md](references/procedure.md) | ||
| - `REFERENCE` → [references/reference.md](references/reference.md) |
There was a problem hiding this comment.
Would it be possible to include the specific guidelines here instead of in separate files? Or does the approach with separate files have any benefits?
There was a problem hiding this comment.
Or actually, how about we pull in modular templates as a separate skill/skill reference, and include these specifics in those templates? Pulling the templates into this repo was proposed before in #4722, and I was against it, but I'm not sure how much longer the modular guides and templates will keep being supported and updates. Perhaps it's time we took ownership of them here as a project resource? Then these abstract instructions could be integrated with the abstract part of each template.
There was a problem hiding this comment.
What do modular templates have to do with the content of short descriptions?
Separating the specific instructions for each type - I did that based on best practices for agent skills.
There was a problem hiding this comment.
Fair enough, I can look into it myself later.
|
|
||
| - Introduce the concept and provide a concise answer to the question "What is this?" and in some cases "Why do I care about this?" | ||
| - If the concept is unfamiliar, start with a brief definition. | ||
| - Avoid using the short description to lead in or build up to a topic. |
There was a problem hiding this comment.
What does this mean? A short description does introduce a topic.
There was a problem hiding this comment.
It's supposed to summarize the topic, not introduce it.
|
|
||
| When the module has `:_mod-docs-content-type: REFERENCE`, follow these rules for the abstract (short description): | ||
|
|
||
| - Briefly describe what the reference item does, what it is, or what it is used for. |
There was a problem hiding this comment.
"reference item" seems unclear
There was a problem hiding this comment.
It's the "thing being referenced in the module". I don't know how else to call it. It seems clear enough to me. I'm open to suggestions.
|
Seems to work well enough for me. |
Co-authored-by: Aneta Petrová <apetrova@redhat.com>
Co-authored-by: Aneta Petrová <apetrova@redhat.com>
Co-authored-by: Aneta Petrová <apetrova@redhat.com> Co-authored-by: Lena Ansorge <zuansorg@redhat.com>
4550ebe to
e688592
Compare
|
Rebased. |
|
I've tested it on #4870 and got quite good results too. Marking it as "testing done". |
|
Since there haven't been any further comments, I'm considering this acked. |
Co-authored-by: Aneta Petrová <apetrova@redhat.com>
Co-authored-by: Aneta Petrová <apetrova@redhat.com>
What changes are you introducing?
Enhancing the abstract AI skill with instructions for DITA short descriptions
Why are you introducing these changes? (Explanation, links to references, issues, etc.)
To achieve higher quality of AI work
Anything else to add? (Considerations, potential downsides, alternative solutions you have explored, etc.)
These instructions come from DITA reference.
Contributor checklists
Please cherry-pick my commits into: